Test Failure: JIT/jit64/opt/cg/cgstress/CgStress1_ro/CgStress1_ro.cmd

[WangyangZhou90]

Failed in:runtime-cet 20240925.1
Error message:

C:\h\w\AB0609D4\w\B16009B0\e\JIT\jit64\jit64_3../opt/cg/cgstress/CgStress1_r/CgStress1_r.cmd
04:12:45.420 Passed test: JIT/jit64/opt/cg/cgstress/CgStress1_r/CgStress1_r.cmd
04:12:45.421 Running test: JIT/jit64/opt/cg/cgstress/CgStress1_ro/CgStress1_ro.cmd

Assert failure(PID 3384 [0x00000d38], Thread: 3696 [0x0e70]): !"If this ever fires, then this method should return HRESULT"

CORECLR! FieldDesc::GetAttributes + 0xFA (0x00007ffcbb62552a) CORECLR! CEEInfo::getFieldInfo + 0x577 (0x00007ffcbb63ef97)
CLRJIT! Compiler::impImportBlockCode + 0x6212 (0x00007ffcbc5caa02) CLRJIT! Compiler::impImportBlock + 0x1AD (0x00007ffcbc5c370d)
CLRJIT! Compiler::impImport + 0x48E (0x00007ffcbc5c2b1e) CLRJIT! Compiler::fgImport + 0x18 (0x00007ffcbc55e848)
CLRJIT! Phase::Run + 0x76 (0x00007ffcbc6bf3a6) CLRJIT! Compiler::compCompile + 0x21F (0x00007ffcbc4e7f1f)
CLRJIT! Compiler::compCompileHelper + 0xA2A (0x00007ffcbc4ebd4a) CLRJIT! Compiler::compCompile + 0x948 (0x00007ffcbc4eab18)
File: D:\a_work\1\s\src\coreclr\vm\field.h:632
Image: C:\h\w\AB0609D4\p\corerun.exe

App Exit Code: -1073740286
Expected: 100
Actual: -1073740286
END EXECUTION - FAILED
FAILED
FAILED
[XUnitLogChecker]: 04:12:47.58: The full run will be done.
[XUnitLogChecker]: 04:12:47.59: Item 'jit64_3' did not finish running. Checking and fixing the log...
[XUnitLogChecker]: 04:12:47.59: XUnit log file has been fixed!

[dotnet-policy-service]

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

[dotnet-policy-service]

Tagging subscribers to this area: @mangod9
See info in area-owners.md if you want to be subscribed.

[mrsharm]

Unassigning the GC team since this seems like a JIT based assertion failure that occurred while running the CET test suite.

CC: @JulieLeeMSFT

[dotnet-policy-service]

Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.

[mangod9]

Oh, I noticed Julie had moved it to VM area. Was this investigated and determined to be not an issue in codegen?

[amanasifkhalid]

Was this investigated and determined to be not an issue in codegen?

As far as I know, nobody on the codegen side has investigated this yet. cc @dotnet/jit-contrib

[EgorBo]

Was this investigated and determined to be not an issue in codegen?

The assert was failing on VM side, that is why it was moved to VM I guess.

[amanasifkhalid]

I cannot reproduce this issue with a mainline build, or with the build from the failing run. The latest run of runtime-cet passed, so maybe this was a one-off?

[JulieLeeMSFT]

The assert was failing on VM side, that is why it was moved to VM I guess.

That is right.

I cannot reproduce this issue with a mainline build, or with the build from the failing run. The latest run of runtime-cet passed, so maybe this was a one-off?

Let's monitor some more runs and close this issue if it doesn't happen again.

[amanasifkhalid]

Let's monitor some more runs and close this issue if it doesn't happen again.

Assigning myself so I remember to check.

[amanasifkhalid]

Let's monitor some more runs and close this issue if it doesn't happen again.

This hasn't reproduced for the last two runs.