Weird repeating of the exact same test when running everything expanded

[kevmoo]

As of 543d9f3

> pub run test -r expanded
00:00 +0: test/backend/declarer_test.dart: .test() declares a test with a description and body
00:00 +1: test/backend/declarer_test.dart: .test() declares a test with a description and body
00:00 +2: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +3: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +4: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +5: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +6: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +7: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +8: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +9: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +10: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +11: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +12: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +13: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +14: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +15: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +16: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +17: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +18: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +19: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +20: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +21: test/backend/metadata_test.dart: onPlatform parses a valid map
00:00 +22: test/backend/metadata_test.dart: onPlatform parses a valid map

But not when running a single file?

> pub run test -r expanded test/runner/pub_serve_test.dart
00:00 +0: with transformed tests runs those tests in the VM
00:05 +1: with transformed tests runs those tests on Chrome
00:21 +2: with transformed tests runs those tests on content shell
00:36 +3: with ... tests gracefully handles pub serve running on the wrong directory for VM tests
00:40 +4: with ... gracefully handles pub serve running on the wrong directory for browser tests
00:45 +5: with transformed tests gracefully handles unconfigured transformers
00:49 +6: uses a custom HTML file on Chrome
01:06 +7: uses a custom HTML file on content shell
01:26 +8: gracefully handles pub serve not running for VM tests
01:29 +9: gracefully handles pub serve not running for browser tests
01:32 +10: gracefully handles a test file not being in test/

[nex3]

This is intended. When you run multiple test suites, they run in parallel; this means that many tests may complete while one test is still running. The expanded reporter represents this by showing the oldest running test whenever a test completes; this ensures that the user is always aware of at least one test that is currently running, so that if there's a deadlock or the tests are just too slow they have visibility into what's going on.