outerloop tests failing to detect `dotnet`

Build

https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=43878

Build leg reported

Invariant.Tests.WorkItemExecution

Pull Request

https://github.com/dotnet/runtime/pull/76707

Action required for the engineering services team

To triage this issue (First Responder / @dotnet/dnceng):

• Open the failing build above and investigate
• Add a comment explaining your findings

If this is an issue that is causing build breaks across multiple builds and would get benefit from being listed on the build analysis check, follow the next steps:

1. Add the label “Known Build Error”
2. Edit this issue and add an error string in the Json below that can help us match this issue with future build breaks. You should use the known issues documentation

{
   "ErrorMessage" : "dotnet: No such file or directory",
   "BuildRetry": false
}

Additional information about the issue reported

• Log example: https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-76707-merge-ba2b60b0919840c898/Invariant.Tests/1/console.8e5f6a78.log?helixlogtype=result
• Output example:

./RunTests.sh: line 168: /tmp/helix/working/A6B808E3/p/dotnet: No such file or directory

Report

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	0	0

[mmitche]

FWIW: the linked PR is adding tests that create 8 GB files (not in parallel to avoid having more than one huge file at the time) so I wonder if that may affect that some dependencies being downloaded fail because VM is out of disk, but I highly doubt it because I assume that at the point the test is run, you already have all the dependencies.

Just wanted to point out what’s “special” about the PR in relation with outerloop.

@Jozkee The outerloop testing has failed in the same way against main (and other branches) for as far back as the AzDO history goes…so my guess is that this is just a test configuration error.

[mmitche]

@MattGal I think it’s been failing as far back as I can see. I think the correlation payload didn’t zip up dotnet in the expected location