-
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
Test failure GC\\Regressions\\Github\\Runtime_76219\\Runtime_76219\\Runtime_76219.cmd #78899
Comments
Tagging subscribers to this area: @dotnet/gc Issue DetailsRun: runtime-coreclr gcstress-extra 20221126.1 Failed test:
Error message:
|
This test verifies that GC doesn't collect an unreferenced frozen object (that becomes referenced again then) |
@cshung as fyi.. |
I took a look at the dump. Here are some high-level findings.
This is x86, so we are running Segments, not regions. I cannot reproduce it locally yet. |
Another dup? #79807 |
Failed again in: runtime-coreclr gcstress-extra 20221221.1 Failed test:
Error message:
|
Another failure: "coreclr OSX arm64 Checked jitstress_isas_nohwintrinsic" @cshung There are lots of bugs for this test case and lots of different failures. Are you keeping the test enabled to collect more data, perhaps crash dumps? Or should we disable the test (for some appropriate subset of platforms) to clean the CI runs? |
Oh, I didn't realize this is actually running in CI. I thought this is a GCStress test case, let me move it out of the regular CI run for now. |
@mangod9 - during our GC sync we want to move this test out of the CI runs into the gcstress extra pipeline so that we can debug by just triggering it. How do we do this? |
Guessing you just have to move it out from p0 or p1 category. @trylek can provide guidance here. |
The test is completely disabled on coreclr after #80399. |
Run: runtime-coreclr gcstress-extra 20221126.1
Failed test:
Error message:
The text was updated successfully, but these errors were encountered: