-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Helix test results are not getting uploaded for a lot of jobs #74699
Comments
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsFor Working case in wasm/runtime-tests:
All the test results are missing, and can't be seen with kusto. This is for wasm, rolling builds, and each column represents a different CI job: Note: the cc @lewing @steveisok @akoeplinger @ViktorHofer
|
This is caused by 7a4b0af#diff-1d68a522b60c1ab69fb537ce06f5d7e9a176fa4f75e16425fc164d4b738d7678 from PR #73060 (which, if you look at the last run of it, didn't run hardly any tests) It made breaking changes in "sendtohelixhelper.proj". Currently runtime has almost ZERO test coverage, so that change should be reverted immediately. |
PR dotnet#73060 broke uploading of helix test results. This was caused by the change: ```xml <HelixPostCommands>@(HelixPostCommand)</HelixPostCommands> ``` This is overwriting the existing value of `$(HelixPostCommands)`, which gets set to have the upload script invocation in https://github.com/dotnet/arcade/blob/34dff939b4a91e4693f78a856e0e055c1a3f3fba/src/Microsoft.DotNet.Helix/Sdk/tools/azure-pipelines/AzurePipelines.MonoQueue.targets#L8-L15 at evaluation time. Fix by *appending* to the property. Thanks to ChadNedzlek for finding the cause! Fixes dotnet#74699 .
* CI: Fix helix test results reporting PR #73060 broke uploading of helix test results. This was caused by the change: ```xml <HelixPostCommands>@(HelixPostCommand)</HelixPostCommands> ``` This is overwriting the existing value of `$(HelixPostCommands)`, which gets set to have the upload script invocation in https://github.com/dotnet/arcade/blob/34dff939b4a91e4693f78a856e0e055c1a3f3fba/src/Microsoft.DotNet.Helix/Sdk/tools/azure-pipelines/AzurePipelines.MonoQueue.targets#L8-L15 at evaluation time. Fix by *appending* to the property. Thanks to ChadNedzlek for finding the cause! Fixes #74699 . * Disable failing tests, see #74781 Co-authored-by: Alexander Köplinger <[email protected]>
For
runtime
pipeline, with rolling builds.Working case in wasm/runtime-tests:
Broken cases
The above 2 cases are not running
reporter/run.py
. The test results can't be seen via kusto.It seems to be working with this, but failing on the next rolling build. And the changes between those - 7b0227d...8755447 .
This is for wasm, rolling builds, and each column represents a different CI job:
Note: the
xharness-event-processor.py
error can be ignored.cc @lewing @steveisok @akoeplinger @ViktorHofer @premun
The text was updated successfully, but these errors were encountered: