bryancall opened a new pull request, #13943: URL: https://github.com/apache/trafficserver/pull/13943
CI splits the Uranium tests into shards by each test's position in the sorted list of test ids. Adding or removing a test moves every test after it to a different shard. Over the last week of master (2ac2edcaea to 0404e4911f), 26 added and 2 removed tests moved 32% of the suite across 3 shards. That matters when one shard fails and only that shard is rerun. If the base has moved in between, the failing test may now sit in a different shard, so the rerun comes back green without having run it. This assigns each test to a shard by a CRC32 hash of its test id instead, so a test keeps its shard as the suite changes. The shards stay close in size: 479, 514 and 480 tests on current master. Every test still lands in exactly one shard; I checked the union of the three shards against the full collection. The new test in `test_plugin.py` adds one test that sorts ahead of 200 others and checks none of them changes shard. It fails on the old selection, where all 200 move. Every test moves once when this merges, then stays put. No Jenkins change is needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
