[rush] Operation Build Cache Log Restoration collision

Start with libraries/rush-lib/src/logic/operations/OperationMetadataManager.ts at the linked location, then reproduce the collision by running the same cacheable operation with different parameters in parallel and rerunning the build. Compare the restored logs for each shard; done means each independent run restores its own logs rather than the logs from another shard.

Summary

Operation Build Cache Log Restoration collision when multiple of same operation with different parameters run in parallel on same filesystem.

We are trying to run multiple of the same operation with different parameters on the same CI agent (for example, rush test:integration--shard=1 --shard-total=3, rush test:integration--shard=2 --shard-total=3, rush test:integration--shard=3 --shard-total=3). We do this to parallelize our tests and take advance of build caching.

This all works, but when restoring from cache, even despite the unique cache keys, the restored logs are all for one of the three shards.

Repro steps

1. Have an operation with custom parameters on command-line, configured as build-cacheable
2. Run multiple of that same operation, with different parameters passed on the same build agent in parallel
3. Re run the build

Expected result:
Restored logs for each of the three independent runs
Actual result:
All three runs have restored logs for just one of the initially passing runs.

Details

I'm fairly certain the problem is here:
https://github.com/microsoft/rushstack/blob/main/libraries/rush-lib/src/logic/operations/OperationMetadataManager.ts#L66

The location on the filesystem is not unique per parameter, only per operation. (This despite the fact that the build cache is in fact parameter aware.

Standard questions

Please answer these questions to help us investigate your issue more quickly: