CI's macOS check runs internal/core/implement/loop as one test process under -race, and it now takes most of the step's 40-minute budget: 2244s on a passing run (Actions run 40821104565), and on 29 Oct a queue entry for pull request 1201 timed out on it (run 40825987527) with no test hung, dropping the change from the merge queue. Preflight already runs the three longest packages as three processes each through internal/testshard (ABCD_TEST_SHARDS=3); CI sets no shards, so every queued change risks the same timeout.

CI's macOS check runs internal/core/implement/loop as one test process under -race, and it now takes most of the step's 40-minute budget: 2244s on a passing run (Actions run 40821104565), and on 29 Oct a queue entry for pull request 1201 timed out on it (run 40825987527) with no test hung, dropping the change from the merge queue. Preflight already runs the three longest packages as three processes each through internal/testshard (ABCD_TEST_SHARDS=3); CI sets no shards, so every queued change risks the same timeout.

Grounds

• pursued: the loop package's slowest shard on the macOS queue run finishes well under the 40-minute -timeout; shown wrong if a shard still nears or crosses it