Open fanyang-mono opened 1 year ago
Hello @fanyang-mono, could you please update the "ErrorMessage" : ""
by following the step by step documentation on how to create a known issue
Updated.
This is duplicate of https://github.com/dotnet/runtime/issues/89409, except here it's not only wasm debugger
@pavelsavara and @fanyang-mono, should this issue be closed in favour of dotnet/runtime#94560❔ if not, the error message isn't sufficiently precise to understand what (if anything) we (DNCEng) could do about it.
@pavelsavara and @fanyang-mono, should this issue be closed in favour of
You mean https://github.com/dotnet/runtime/issues/89409
I think we should keep this one, because this one has some hits which are not just wasm debugger related. Here we see other repo failures, on roslyn and aspnetcore CI.
if not, the error message isn't sufficiently precise to understand what (if anything) we (DNCEng) could do about it.
I have not investigated it myself yet. But got questions which could help to narrow it down
This issue was originally created to track issues happened to wasm debugger tests (belonging to dotnet/runtime
repo). However, the error message was generic enough to include issues from other repos, such as dotnet/roslyn
and dotnet/aspnetcore
. We need insights from owners from dotnet/roslyn
and dotnet/aspnetcore
to confirm that they are aware of these issue. And if they are okay to close this issue as well. We could close then.
We just got an instance of this in the dotnet/aspire
repo. It wasn't a WASM related failure for us. Just looks like the test process crashed and took a few tests with it.
Build
https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=351450
Build leg reported
chrome-DebuggerTests.EvaluateOnCallFrameTests.WorkItemExecution
Pull Request
https://github.com/dotnet/runtime/pull/89217
Known issue core information
Fill out the known issue JSON section by following the step by step documentation on how to create a known issue
@dotnet/dnceng
Release Note Category
Release Note Description
Additional information about the issue reported
No response
Report
Summary
Known issue validation
Build: :mag_right: Result validation: :warning: Validation could not be done without an Azure DevOps build URL on the issue. Please add it to the "Build: :mag_right:" line. Validation performed at: 2/8/2024 9:24:30 PM UTC