-
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
Assertion failed: (*card_word)==0 in DynamicGenerics tests #76801
Comments
Tagging subscribers to this area: @dotnet/gc Issue Details
Failed in #76799. Full log: https://dev.azure.com/dnceng-public/public/_build/results?buildId=45701&view=logs&jobId=58dc7ccb-0414-5dd3-62a5-bf2e63258b7c&j=ea7d6d51-d18d-5306-47bd-e3b7db04467e&t=3c9d9518-9046-50a7-9208-2e9137da71b6 {
"ErrorMessage": "(*card_word)==0",
"BuildRetry": false
}
|
@dotnet/gc I suspect that this may be related to regions and frozen objects. Could you please review |
I assume it started to appear after #76737 ? |
Assigning to Maoni assuming its related to enabling regions on NativeAOT? |
Andrew is looking at this. |
I also think there's something wrong with reporting - I saw this in my recent PR testing and while detailed scrutiny of the log ultimately revealed the assertion failure, the summary at the end of the log says cmdLine:D:\a\_work\1\s\artifacts\tests\coreclr\windows.x64.Checked\nativeaot\SmokeTests\DynamicGenerics\DynamicGenerics\DynamicGenerics.cmd Timed Out (timeout in milliseconds: 1800000 from variable __TestTimeout, start: 10/12/2022 8:44:52 PM, end: 10/12/2022 9:14:52 PM) Test Harness Exitcode is : -100 A possible explanation is that in my testing the assertion failure happened very close to the 30 minute timeout for the test. |
I noticed that when the assertion happened on my machine, it stuck at a dialog box, so that might explain the timeout. |
Thanks Andrew, I guess that explains a lot, in CoreCLR testing we're going a long way towards suppressing all such dialogs by disabling WER UI and by other means, it might be the case that the relatively recent NativeAOT testing is still missing some of these measures. |
Still stuck with this one, but I found something interesting. It appears that when the assertion happens, the line being printed is always this: |
NativeAOT on Windows is building with hardware write watch currently. It does not build with |
I was surprised to see that these 2 defines are not defined for AoT. it does expose a bug with regions (when we make |
Before #77224, I am able to reproduce the bug locally in a few minutes. After the fix, I am unable to repro it locally for 4 hours. Closing this issue opportunistically to see if that repro again. Feel free to reopen if the bug repros. |
Failed in #76799 (windows.x64.Checked). Full log: https://dev.azure.com/dnceng-public/public/_build/results?buildId=45701&view=logs&jobId=58dc7ccb-0414-5dd3-62a5-bf2e63258b7c&j=ea7d6d51-d18d-5306-47bd-e3b7db04467e&t=3c9d9518-9046-50a7-9208-2e9137da71b6
Report
Summary
The text was updated successfully, but these errors were encountered: