Logging in console test to help understand #60240

[danmoseley]

Relates to #60240

Hopefully this won't break the repro.

[ghost]

Tagging subscribers to this area: @dotnet/area-system-console
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Relates to #60240

Hopefully this won't break the repro.

Author:	danmoseley
Assignees:	danmoseley
Labels:	area-System.Console
Milestone:	-

[jkotas]

Hopefully this won't break the repro.

This change breaks the repro.

It repros 100% of the time before this change for me. It never repros for me after this change.

Repro steps:

build.cmd -c Release -rc checked -arch x86 -s clr+libs+libs.pretest+libs.tests
cd src\libraries\System.Console\tests
set COMPlus_TieredCompilation=0
set COMPlus_JitStressRegs=1
dotnet build /t:Test /p:TargetArchitecture=x86 -c Release

This is JIT register allocator stress bug. FWIW, I do not think that logging like this will help with investigation. The JIT folks will need the disassembly and the JIT log to figure out the problem.

[danmoseley]

Ah interesting. Meantime, we presumably don't want to leave tests failing. I can revert the logging, if there's a better way to stop the failure.

[jkotas]

Disable the test against the issue using RuntimeTestModes.JitStressRegs (https://github.com/dotnet/arcade/blob/main/src/Microsoft.DotNet.XUnitExtensions/src/RuntimeTestModes.cs#L21).