-
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 Loader/classloader/StaticVirtualMethods/GenericContext/GenericContextTest/GenericContextTest.sh #53161
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Historical failures of this test:
More failures
|
Tagging subscribers to this area: @vitek-karas, @agocke, @CoffeeFlux, @VSadov Issue DetailsRun: runtime-coreclr gcstress-extra 20210522.1 Failed test:
Error message:
|
Failed again in runtime 20210531.42 Failed test:
Error message:
Historical failures of this test has updated in this comment. |
Turning this into a tracking issue. This shows up as a bad one for reliability currently. |
cc: @agocke |
@trylek this looks like static virtual methods issue - can you please take a look (also what area are we using for that feature)? |
Sure, will do, I think that for starters we should put this under the area-vm-coreclr label even though it may turn out to be arm-specific and merit a different categorization based on the initial investigation. |
I cannot reproduce the failure on Linux arm64 Checked (tried gcstress0xc_zapdisable_jitstress2 and some other variations) and I see no recent failures or actionable core dumps. |
Sounds good, let's close for now and we can re-open if problems reappear |
Run: runtime-coreclr gcstress-extra 20210522.1
Failed test:
Error message:
Runfo Tracking Issue: loader/classloader/staticvirtualmethods/genericcontext/genericcontexttest/genericcontexttest.sh
Build Result Summary
The text was updated successfully, but these errors were encountered: