Skip to content

Conversation

@AntonLapounov
Copy link
Member

The test assumed that all allocated P and Q objects are collected during the same GC pass (Q.first_p_count == P.count), which may not be the case under GC stress. The fix is to unroot all allocated objects at the same time. I also fixed indentation, improved naming, and moved the test to the existing finalization directory.

Fixes #75782.

@ghost ghost added the area-VM-coreclr label Sep 21, 2022
@ghost ghost assigned AntonLapounov Sep 21, 2022
Copy link
Member

@VSadov VSadov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!!

@EgorBo
Copy link
Member

EgorBo commented Sep 22, 2022

@AntonLapounov looks like it's still failing? e.g. in #75573 and other PRs ^

@fanyang-mono
Copy link
Member

@radical This PR changed runtime tests; but the mono runtime tests CI lanes weren't triggered in this PR. Could you please check?

@AndyAyersMS
Copy link
Member

Still failing for me too... #75992 (x86 windows).

@AntonLapounov
Copy link
Member Author

I opened #76041 for the new intermittent failure.

@ghost ghost locked as resolved and limited conversation to collaborators Oct 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

critical_finalization tests fails with GCStress=0x3

5 participants