-
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
Test failure: GC\\Features\\HeapExpansion\\Finalizer\\Finalizer.cmd #102706
Comments
Tagging subscribers to this area: @dotnet/gc |
Failed in: runtime-coreclr jitstress-isas-x86 20240601.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20240603.6 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr jitstress 20240603.2 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr r2r 20240604.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr pgo 20240608.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr jitstress-isas-x86 20240615.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr pgo 20240619.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr jitstressregs 20240623.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr jitstress-isas-x86 20240629.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20240701.2 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr outerloop 20240702.9 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr jitstress 20240703.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr jitstress-isas-x86 20240706.2 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr jitstress 20240710.3 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr jitstress-isas-x86 20240713.1 Failed tests:
Error message:
Stack trace:
|
Failed in: runtime-coreclr r2r-extra 20240714.1 Failed tests:
Error message:
Stack trace:
|
@cshung what is the status of this? It has been blocking CI for quite a long time at this point. |
As a team, we are not prioritizing on 32-bit platforms related work, investigating this bug will likely require quite a bit of work, Is this assertion blocking anything important? We can comment out the assertion easily. |
Yes, it is blocking clean CI runs.
That would be good. Generally blocking-clean-ci[-optional] issues should be made non-blocking with high priority since these issues cause disruption to people filing PRs in the repo. |
Failed in: runtime-coreclr jitstressregs 20240526.1
Failed tests:
Error message:
Stack trace:
Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=687884
Error message validated:
[new_current_total_committed_bookkeeping == current_total_committed_bookkeeping
]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 5/31/2024 1:30:58 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: