-
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 JIT/Directed/lifetime/lifetime1/lifetime1.sh #54042
Labels
Milestone
Comments
dotnet-issue-labeler
bot
added
area-crossgen2-coreclr
untriaged
New issue has not been triaged by the area owner
labels
Jun 11, 2021
This is failing for Linux arm32/arm64/x64 in GCStress=F. More cases: @dotnet/crossgen-contrib |
Looking at the test in more depth, this appears to be a test bug, not a product bug. Crossgen2 is used with the optimizer enabled, which will causes what I believe to be completely normal behavior, where the A object is freed naturally. |
Failed again in runtime-coreclr r2r-extra 20210703.1 Failed test:
Error message:
|
BruceForstall
added a commit
to BruceForstall/runtime
that referenced
this issue
Jul 8, 2021
The test assumed that a GC didn't occur between the last use of a variable and a check of a value set in the finalizer. This presumably worked up until now because the test is set to build in debuggable code mode. But R2R compilations ignore that and build with optimization enabled, and GCStress exposes the issue. Fix the test by explicitly marking a variable as KeepAlive until after the requisite check. Fixes dotnet#54042
Merged
ghost
added
the
in-pr
There is an active PR which will close this issue when it is merged
label
Jul 8, 2021
BruceForstall
added a commit
that referenced
this issue
Jul 9, 2021
The test assumed that a GC didn't occur between the last use of a variable and a check of a value set in the finalizer. This presumably worked up until now because the test is set to build in debuggable code mode. But R2R compilations ignore that and build with optimization enabled, and GCStress exposes the issue. Fix the test by explicitly marking a variable as KeepAlive until after the requisite check. Fixes #54042
ghost
removed
the
in-pr
There is an active PR which will close this issue when it is merged
label
Jul 9, 2021
ghost
locked as resolved and limited conversation to collaborators
Aug 8, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Run: runtime-coreclr r2r-extra 20210610.1
Failed test:
Error message:
The text was updated successfully, but these errors were encountered: