-
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/HardwareIntrinsics/X86/Avx2/Avx2_ro/Avx2_ro.sh #57462
Comments
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsRun: runtime-coreclr gcstress0x3-gcstress0xc 20210815.1 Failed test:
Error message:
|
CC @dotnet/jit-contrib |
Most of the failures in the issue are due to timeouts - we've seen such in the past with the GCStress jobs. The only "interesting" one here is Regressions\coreclr\GitHub_45929\test45929\test45929.cmd - it timed out on multiple platforms - Linux-x64, macOS-arm64, Windows-x86 and Windows-Arm64. |
The Regressions\coreclr\GitHub_45929 test runs veeeery slowly under
and it's still in progress... I don't know if it's expected - @janvorli can you please comment since you've added the test? |
Regressions\coreclr\GitHub_45929 test took 6 hours on my machine to complete (successfully) - EDIT: Found related issue - #46803 |
I ran locally other tests in the issue that were failing with timeouts and don't see any issue there. I suspect these could be transient failures (the Avx2_ro and Sse2_ro tests suites are huge and they can occasionally exceed the timeouts set on the jobs). Moving the issue to 7.0 to keep an eye on the test for now. |
Failed again in: runtime-coreclr gcstress0x3-gcstress0xc 20210822.1 Failed test:
Error message:
or
or
|
Failed again in: runtime-coreclr r2r 20210825.1 Failed test:
Error message:
|
Yes, it is expected due to the level of stress it does. It does a lot of exception dispatching using ExceptionDispatchInfo. 1 million times in parallel on each available processor. The purpose of this test is to stress the exception dispatching to verify that there is no race in generating watson buckets. Just the stressy nature of this test seems to uncover an unrelated rare GC issue that we are seeing here. |
Failed again in: runtime-coreclr gcstress0x3-gcstress0xc 20210905.1 Failed test:
Error message:
|
Failed again in: runtime-coreclr r2r-extra 20210912.1 Failed test:
Error message:
|
Failed again in: runtime-coreclr r2r 20210920.1 Faile test:
Error message:
|
Unfortunately, it looks like this issue now contains a mix of failures, both Avx2 & friends, mostly (exclusively?) timeouts, and Test45929 on Windows/arm32 with a real-looking GC hole assert (note: we don't formally support Windows/arm32 anymore). |
Failed again in: runtime-coreclr gcstress0x3-gcstress0xc 20210925.1 Failed test:
Error message:
|
Failed again in: runtime-coreclr r2r-extra 20211010.1 Failed test:
One of error message:
|
Duplicate of #60154 |
Run: runtime-coreclr gcstress0x3-gcstress0xc 20210815.1
Failed test:
Error message:
The text was updated successfully, but these errors were encountered: