-
Notifications
You must be signed in to change notification settings - Fork 358
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
Test known issue not displayed #10537
Comments
@ulisesh thinking that the known issue isn't being picked up because the error is in the work item logs? (I haven't investigated Juan's issue, however) |
Sorry - I am not saying there's an issue with the JSON + Tag. That wouldn't work as you said. However, the issue has been seen in other PRs within a few days - it's just not easy to identify since it's a whole workitem crash. |
Now that we have support for known issues for tests build analysis should be able to identify this error. A known issues with the correct label and the error string like StreamShutdown failed: QUIC_STATUS_INVALID_PARAMETER should be enough. @hoyosjs we are very interested in seeing this working as we just release the feature. If the error string make sense, can you please update your issue with the label and JSON blob? |
Oh, I know it was stages to roll out but didn't know it was out in the wild. Will do. Thanks! |
@ulisesh can you please check if I did somehting wrong: dotnet/runtime#73688 |
The issue has everything it needs, I'll check why build analysis isn't finding any hits |
Turns out that there is a bug in build analysis that prevents test known issues from being displayed, I'll fix it but unfortunately the fix will be roll out next Wednesday. FYI, this is how we were expecting the known issue to be showed https://gist.github.com/ulisesh/1b616e4188ef0af87b05fe7e1e99c989 @hoyosjs, thanks for working with us |
Rolled out |
A negative sentiment was registered against feature: DeveloperWorkflowGitHubCheckTab
Failure undetected - It's a known issue as of 12 days ago: dotnet/runtime#73688; I know it's hard since it's a whole workitem failure and not just a test. Likely needs business logic for it to be actionable, like helix log search.
Feedback submitted by @hoyosjs, who requested further communication regarding this issue.
Parameters
c = ab5bf51d79fc
rb = 0
rt = 0
ub = 0
e = 0
r = dotnet/runtime
s = 2022-08-22T13-22-18
ki = 0
ut = 1
The text was updated successfully, but these errors were encountered: