runtime: JIT/Methodical/Boxing/misc/concurgc.il failing in CI with a timeout
Hit this on a PR I opened, and saw that it also happened on another recent job. Here are the two instances:
https://ci.dot.net/job/dotnet_coreclr/job/master/job/x86_checked_windows_nt_prtest/3373/ https://ci.dot.net/job/dotnet_coreclr/job/master/job/x86_checked_windows_nt_prtest/3369/
cmdLine:D:\j\workspace\x86_checked_w---b3a226f6\bin\tests\Windows_NT.x86.Checked\JIT\Methodical\Boxing\misc\_relconcurgc_il\_relconcurgc_il.cmd Timed Out
18:42:02 Test Harness Exitcode is : -100
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 20 (20 by maintainers)
Commits related to this issue
- Fix some cross-thread memory accesses in a JIT test. This test was concurrently accessing shared memory without using appropriate volatile accesses. This change adds the `volatile.` prefix where nece... — committed to pgavlin/coreclr by pgavlin 7 years ago
- Fix Issue #10022. This issue occurred because the JIT currently inserts the P/Invoke method prolog into the first block of a function without ensuring that this block will only execute once. This is ... — committed to pgavlin/coreclr by pgavlin 7 years ago
- Fix Issue #10022. (#10587) This issue occurred because the JIT currently inserts the P/Invoke method prolog into the first block of a function without ensuring that this block will only execute onc... — committed to dotnet/coreclr by pgavlin 7 years ago
- Fix some cross-thread memory accesses in a JIT test. This test was concurrently accessing shared memory without using appropriate volatile accesses. This change adds the `volatile.` prefix where nece... — committed to guhuro/coreclr by pgavlin 7 years ago
We have
fgEnsureFirstBBisScratch()to do stuff like this.