The test file jstests/core/query/release_memory/group.js relies on the global server status spilling metrics not being modified by any background query activity while the test is executing.

The test file contains several tests like the following (pseudo-code)

setGlobalSpillingServerParameter(config);
old = getSpillCounter();
runQuery(pipeline);
new = getSpillCounter();
assert.eq(old, new);

This assumes that running the query does not affect the global spilling metrics in the server status. While this can be ensured for the queries executed by the test, it cannot be ensured for background/system queries that are executing in parallel.
Any concurrently running background query can modify the global spilling metrics as well.
There is not much that can be done about this except retrying the test case.

We should add a few retries to the test cases here, so they become less flaky when there is background activity.