The particular test is already fixed, but the issue seems to have multiple different test cases lumped together.