`shard_store_test` fails on devices with limited resources

I'm getting

//nativelink-store:integration_tests/shard_store_test_test               FAILED in 16.0s
  /home/jaro/.cache/bazel/_bazel_jaro/1b6c0a8d0dc239bb6acb288789218790/execroot/_main/bazel-out/k8-fastbuild/testlogs/nativelink-store/integration_tests/shard_store_test_test/test.log

Executed 54 out of 54 tests: 53 tests pass and 1 fails locally.

even though the logs show that the test runs just fine

exec ${PAGER:-/usr/bin/less} "$0" || exit 1
Executing tests from //nativelink-store:integration_tests/shard_store_test_test
-----------------------------------------------------------------------------

running 15 tests
test has_with_many_digests_both_missing ... ok
test get_part_reads_store0 ... ok
test upload_download_has_check ... ok
test get_part_reads_store1 ... ok
test has_with_many_digests_one_missing ... ok
test has_with_one_digest ... ok
test upload_store1 ... ok
test upload_store0 ... ok
test has_with_many_digests_both_exist ... ok
test weights_send_to_proper_store ... ok
test verify_weights_mid_left_bias ... ok
test verify_weights_even_weights ... ok
test verify_weights_right_bias ... ok
test verify_weights_mid_right_bias ... ok
test verify_weights_left_bias ... ok

test result: ok. 15 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 2.75s

Start by running the //nativelink-store:integration_tests/shard_store_test_test target and inspect its test.log on a resource-limited device. Compare the reported failure with the 15 shard_store tests and determine why the target fails despite all tests reporting success. Done means the target passes reliably under limited-resource conditions.