first of all - kudos for the great work with 2.0, I’m loving the layer caching!
We’re using the test-results-store step in our config (docker executor, remote docker setup, reusable environment) and it seems the test results are accumulating for rebuilds over the same commit.
The step output includes a path that looks like this:
Hash-1 doesn’t seem to change over time. Hash-2 is identical to the one in CIRCLE_ENV, and only seems to change with the next commit. Thus if I re-run the same build, I can see the test results from the past build, too.
Is this intended or there something I’m missing/configuring wrong?