Currently, the linux-race job is consistently failing in GitHub actions (with exit code 143 - SIGTERM).

For example, a CI run with verbose logging enabled fails with the following:

2022-12-01T17:39:21.3663768Z make: *** [Makefile:22: test] Terminated
2022-12-01T17:39:21.5137635Z ##[error]Process completed with exit code 143.
2022-12-01T17:39:21.5192954Z ##[error]The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
2022-12-01T17:39:21.7086950Z Cleaning up orphan processes

Initial indications point at 7d9a5b2, though the same failure mode has been observed on branches without this commit (see here).

Pure speculation: we're crossing some kind of GH Action resource limit when running race, which results in the platform sending a SIGTERM to the make process, which fails the test.

See this internal thread for more context.