-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Link to Failure log is not always present in Send to Helix logs of the failed CI runs #45357
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
I have no idea if this is somehow related, but when I try to re-run the failing tests locally I can see that the number of failed tests is not zero, but the build is reported as successful (I remember some issues with Helix related to program exit code):
|
Tagging subscribers to this area: @ViktorHofer Issue DetailsI've sent a very simple PR and the CI went red: https://github.com/dotnet/runtime/pull/45281/checks?check_run_id=1465351303 So I wanted to find out which tests has failed, but I was unable to find the failed test in the logs Example of log with no link to the failed tests:
I've asked @krwq for a sanity check and he found out that WASM builds produce the link to failed tests:
cc @ViktorHofer
|
This was a side-effect of #45164. We agree it's confusing and we'll fix it, in the meantime you can view the test failures by going to the "Tests" tab in the Azure DevOps build summary page. (note: the reason why you still see the console log in WASM builds is because they use a different way of running the tests). |
The link to the console log is printed again now. |
I've sent a very simple PR and the CI went red: https://github.com/dotnet/runtime/pull/45281/checks?check_run_id=1465351303
So I wanted to find out which tests has failed, but I was unable to find the failed test in the logs
Example of log with no link to the failed tests:
I've asked @krwq for a sanity check and he found out that WASM builds produce the link to failed tests:
cc @ViktorHofer
The text was updated successfully, but these errors were encountered: