-
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
[wasm][debugger] DebuggerTests.AssignmentTests.InspectVariableBeforeAndAfterAssignment
failing
#64188
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsFailing on rolling build - Build, and Log
The runtime is asserting at https://github.com/dotnet/runtime/blob/main/src/mono/mono/component/debugger-agent.c#L2195:
This was hit on the rolling build for 4a6d169 but was working on the previous build for 5605bdf , and the new commit being: 4a6d169
|
@lambdageek or @fanyang-mono I'm going to need some help here. I've no idea why the
The code being executed under that test is runtime/src/mono/wasm/debugger/tests/debugger-test/debugger-assignment-test.cs Lines 158 to 165 in d964b63
|
Cc @thaystg |
I'm working on it. |
@AaronRobinsonMSFT it's possibly unrelated with that commit. Still working on it. |
I didn't see the failure on the subsequent rolling build, so removing |
Seeing this on windows too - log.
|
This is continuing to show up in rolling builds - see the associated builds in the original issue up top. Do we have confirmation that it's introduced by the ref field changes? Could we revert the changes that are causing these or temporarily disable the tests to unblock ci? |
Just an FYI, this issue is not limited to just the testing framework. I'm experiencing it at runtime in my Blazor apps. |
Can you please file a separate issue with the details? |
I can, I just wanted to point out that the problem is not in the test runners themselves but in .NET 6.0. IN case you were trying to trace down a test problem. |
I haven't seen this recently, but hit it today on #63894 . build:
This time
|
This is being hit again, but with a different error:
Also here. |
Issue: dotnet#64188 `DebuggerTests.AssignmentTests.InspectVariableBeforeAndAfterAssignment(clazz: "MONO_TYPE_ENUM"...` - And add some debug bits to help with debugging this on CI.
* [wasm] Disable failing debugger test Issue: #64188 `DebuggerTests.AssignmentTests.InspectVariableBeforeAndAfterAssignment(clazz: "MONO_TYPE_ENUM"...` - And add some debug bits to help with debugging this on CI. * cleanup
@missymessa I looked at the top few builds referenced in the Report (in the PR description), and I don't see the failure Example - https://dev.azure.com/dnceng-public/public/_build/results?buildId=82673&view=results, and https://dev.azure.com/dnceng-public/public/_build/results?buildId=82735&view=results. |
The error message has to improve, build analysis will match this known issue with any failed build or test that contains the string A better error message would be |
I have removed the |
@thaystg what is the status on this one? |
I will close this one, me and @radical haven't seen this recently. |
Failing on rolling build - Build, and Log
The runtime is asserting at https://github.com/dotnet/runtime/blob/main/src/mono/mono/component/debugger-agent.c#L2195:
This was hit on the rolling build for 4a6d169 but was working on the previous build for 5605bdf , and the new commit being: 4a6d169
cc @AaronRobinsonMSFT
Report
Summary
The text was updated successfully, but these errors were encountered: