You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Test failure: Interop/COM/ComWrappers/API/ComWrappersTests/ComWrappersTests.cmd #133331
It suggests that the new test is flaky. This failure was hit by GC stress run that triggers the GC more aggressively. GC stress runs amplify flakiness of tests sensitive to GC timing.
Does AssertUsableAndDrop method in the test make assumptions about the GC timing? ie if you add GC.Collect call after every line in the test, is it still going to pass?
Note that the GC can be triggered anytime due to the background activity like tracing.
Activity
dotnet-policy-service commentedon Sep 7, 2026
Tagging subscribers to this area: @dotnet/interop-contrib
See info in area-owners.md if you want to be subscribed.
jkotas commentedon Sep 7, 2026
New test introduced by #133164 cc @Sergio0694
Sergio0694 commentedon Sep 7, 2026
Just so I understand, was this detected by running some different jobs than what a PR triggers? Because this was green in my PR 🤔
jkotas commentedon Sep 7, 2026
It suggests that the new test is flaky. This failure was hit by GC stress run that triggers the GC more aggressively. GC stress runs amplify flakiness of tests sensitive to GC timing.
Does AssertUsableAndDrop method in the test make assumptions about the GC timing? ie if you add GC.Collect call after every line in the test, is it still going to pass?
Note that the GC can be triggered anytime due to the background activity like tracing.
Fix GC lifetime in ComWrappers cache cleanup test