runtime: Test failure JIT\\HardwareIntrinsics\\General\\Vector256\\Vector256_r\\Vector256_r.cmd
Run: runtime-coreclr jitstress 20220926.3
Failed test:
coreclr windows x64 Checked zapdisable @ Windows.10.Amd64.Open
- JIT\\HardwareIntrinsics\\General\\Vector256\\Vector256_r\\Vector256_r.cmd
Error message:
Return code: 1
Raw output file: C:\h\w\B3BB09D9\w\A3F60922\uploads\Reports\JIT.HardwareIntrinsics\General\Vector256\Vector256_r\Vector256_r.output.txt
Raw output:
BEGIN EXECUTION
"C:\h\w\B3BB09D9\p\corerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" Vector256_r.dll
Beginning test case Abs.Byte at 9/27/2022 7:13:05 AM
Random seed: 20010415; set environment variable CORECLR_SEED to this value to repro
Beginning scenario: RunBasicScenario_UnsafeRead
Beginning scenario: RunReflectionScenario_UnsafeRead
Beginning scenario: RunClsVarScenario
Beginning scenario: RunLclVarScenario_UnsafeRead
Beginning scenario: RunClassLclFldScenario
Beginning scenario: RunClassFldScenario
Beginning scenario: RunStructLclFldScenario
Beginning scenario: RunStructFldScenario
Ending test case at 9/27/2022 7:13:06 AM
Beginning test case Abs.Double at 9/27/2022 7:13:06 AM
Random seed: 20010415; set environment variable CORECLR_SEED to this value to repro
Beginning scenario: RunBasicScenario_UnsafeRead
Beginning scenario: RunReflectionScenario_UnsafeRead
Beginning scenario: RunClsVarScenario
Beginning scenario: RunLclVarScenario_UnsafeRead
Beginning scenario: RunClassLclFldScenario
Beginning scenario: RunClassFldScenario
Beginning scenario: RunStructLclFldScenario
Beginning scenario: RunStructFldScenario
Ending test case at 9/27/2022 7:13:07 AM
Beginning test case Abs.Int16 at 9/27/2022 7:13:07 AM
Random seed: 20010415; set environment variable CORECLR_SEED to this value to repro
Beginning scenario: RunBasicScenario_UnsafeRead
Beginning scenario: RunReflectionScenario_UnsafeRead
Beginning scenario: RunClsVarScenario
Beginning scenario: RunLclVarScenario_UnsafeRead
Beginning scenario: RunClassLclFldScenario
Beginning scenario: RunClassFldScenario
Beginning scenario: RunStructLclFldScenario
Beginning scenario: RunStructFldScenario
Ending test case at 9/27/2022 7:13:07 AM
Beginning test case Abs.Int32 at 9/27/2022 7:13:07 AM
Random seed: 20010415; set environment variable CORECLR_SEED to this value to repro
Beginning scenario: RunBasicScenario_UnsafeRead
Beginning scenario: RunReflectionScenario_UnsafeRead
Beginning scenario: RunClsVarScenario
Beginning scenario: RunLclVarScenario_UnsafeRead
Beginning scenario: RunClassLclFldScenario
Beginning scenario: RunClassFldScenario
Beginning scenario: RunStructLclFldScenario
Beginning scenario: RunStructFldScenario
Ending test case at 9/27/2022 7:13:07 AM
Beginning test case Abs.Int64 at 9/27/2022 7:13:07 AM
Random seed: 20010415; set environment variable CORECLR_SEED to this value to repro
Beginning scenario: RunBasicScenario_UnsafeRead
Beginning scenario: RunReflectionScenario_UnsafeRead
Beginning scenario: RunClsVarScenario
Beginning scenario: RunLclVarScenario_UnsafeRead
Beginning scenario: RunClassLclFldScenario
Beginning scenario: RunClassFldScenario
Beginning scenario: RunStructLclFldScenario
Beginning scenario: RunStructFldScenario
Ending test case at 9/27/2022 7:13:07 AM
Beginning test case Abs.SByte at 9/27/2022 7:13:07 AM
Random seed: 20010415; set environment variable CORECLR_SEED to this value to repro
Beginning scenario: RunBasicScenario_UnsafeRead
Beginning scenario: RunReflectionScenario_UnsafeRead
Beginning scenario: RunClsVarScenario
Beginning scenario: RunLclVarScenario_UnsafeRead
Beginning scenario: RunClassLclFldScenario
Beginning scenario: RunClassFldScenario
Beginning scenario: RunStructLclFldScenario
Beginning scenario: RunStructFldScenario
Ending test case at 9/27/2022 7:13:07 AM
Beginning test case Abs.Single at 9/27/2022 7:13:07 AM
Random seed: 20010415; set environment variable CORECLR_SEED to this value to repro
Beginning scenario: RunBasicScenario_UnsafeRead
Beginning scenario: RunReflectionScenario_UnsafeRead
Beginning scenario: RunClsVarScenario
Beginning scenario: RunLclVarScenario_UnsafeRead
Beginning scenario: RunClassLclFldScenario
Beginnin
Stack trace
at JIT_HardwareIntrinsics._General_Vector256_Vector256_r_Vector256_r_._General_Vector256_Vector256_r_Vector256_r_cmd()
at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)
{
"ErrorMessage":"JIT.HardwareIntrinsics\\General\\Vector256\\Vector256_",
"BuildRetry": false
}
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 0 | 15 |
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 68 (66 by maintainers)
Commits related to this issue
- Temporary instrumentation for #76280 — committed to jkotas/runtime by jkotas 2 years ago
- Temporary instrumentation for #76280 (#77365) — committed to dotnet/runtime by jkotas 2 years ago
- Delete temporary instrumentation for #76280 Fixes #76280 — committed to jkotas/runtime by jkotas 2 years ago
- Delete temporary instrumentation for #76280 (#78537) Fixes #76280 — committed to dotnet/runtime by jkotas 2 years ago
I have pushed more instrumentation to #76656 and #76701 .
I see that you are trying to revert some SIMD related PRs. That can give us some insights too.
The consistent pattern is that the low 23 bits of the higher 2 qwords are zeroed out. 23 bits is unusual number. Where can it come from?
I have a new hit with dump and extra logging in https://github.com/dotnet/runtime/pull/76701. It is with last day worth of changes reverted - something in last day made it less likely to repro.
The extra stresslog confirmed that the value is not getting corrupted in reflection stack. Extra logging: https://github.com/dotnet/runtime/pull/76701/commits/ef2c1e555ea79cd6a484f64ca4056c3df39f60ac#diff-199bd9c252aff6a1808d8d5195faad752fd7df58f290f5c3824cd0c76732372cR738-R747
Next step: Try to get a hit with extra verbose runtime logging to check for any thread suspension or background GC activity.
Notably I have a nice fancy BIOS switch that lets my toggle ERMSB. Toggling it on nor off seems to have any impact, I can’t repro this for any of the configurations that CI has hit it on.
I likewise ran this in a simple powershell script overnight last night with no repro. Notably, I’m on Win 11 22H2. The CI machines look to be
Windows-10-10.0.14393-SP0