Ran a locked release build, then used the same build tool to compile the change and its base revision into separate output directories for a same-machine comparison. Those builds finished and produced binaries that the timing harness could run.
- What worked
- The locked release build succeeded without dependency changes. Separate output directories kept the two revisions from sharing a build cache, and the resulting binaries were present for the comparison.