Test failure System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages

[v-wenyuxu]

Failed in: runtime-coreclr libraries-jitstress 20230629.1

Failed tests:

net8.0-windows-Release-arm64-CoreCLR_checked-jitstress1_tiered-Windows.11.Arm64.Open
    - System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
net8.0-windows-Release-arm64-CoreCLR_checked-tailcallstress-Windows.11.Arm64.Open
    - System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
net8.0-windows-Release-arm64-CoreCLR_checked-jitstress2_tiered-Windows.11.Arm64.Open
    - System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
net8.0-windows-Release-arm64-CoreCLR_checked-no_tiered_compilation-Windows.11.Arm64.Open
    - System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
net8.0-windows-Release-arm64-CoreCLR_checked-zapdisable-Windows.11.Arm64.Open
    - System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
net8.0-windows-Release-arm64-CoreCLR_checked-jitstress2-Windows.11.Arm64.Open
    - System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
net8.0-windows-Release-arm64-CoreCLR_checked-jitstress1-Windows.11.Arm64.Open
    - System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
net8.0-windows-Release-arm64-CoreCLR_checked-jitminopts-Windows.11.Arm64.Open
    - System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages

Error message:

Assert.Equal() Failure
                                 ↓ (pos 42)
Expected: ···c9-a094-de53168c96d0
Actual:   ···c9-a094-de53168c96d0\0
                                 ↑ (pos 42)

Stack trace:

   at System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages() in /_/src/libraries/System.Diagnostics.EventLog/tests/EventLogMessagesTests.cs:line 80
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodInvoker.cs:line 59

{
  "ErrorMessage": "CanReadAndWriteMessages",
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": true
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=324820
Error message validated: CanReadAndWriteMessages
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/4/2023 1:24:41 AM UTC

Report

Build	Definition	Test	Pull Request
356430	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
354230	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
353408	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
342975	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
342104	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
341300	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages	#88854
339891	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
339787	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages	#88854
338978	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
338961	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
337931	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
336908	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
336356	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
334957	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
334721	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
334256	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
334061	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
331369	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
331172	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
330937	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
330588	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
330527	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
330480	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
330387	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
329962	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
329717	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages	#88345
329704	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages	#84122
329472	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
329439	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
329361	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages	#88345
329210	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
329047	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages	#88380
328828	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages	#88322
328822	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
328776	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
328678	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages	#88345
328529	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
328483	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages	#88354
328443	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages	#88322
328406	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages	#88345
328385	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages	#88342
328094	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages	#88322
327993	dotnet/runtime	System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages	#88184

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	3	43

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

Issue Details

---

Failed in: runtime-coreclr libraries-jitstress 20230629.1

Failed tests:

net8.0-windows-Release-arm64-CoreCLR_checked-jitstress1_tiered-Windows.11.Arm64.Open
    - System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
net8.0-windows-Release-arm64-CoreCLR_checked-tailcallstress-Windows.11.Arm64.Open
    - System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
net8.0-windows-Release-arm64-CoreCLR_checked-jitstress2_tiered-Windows.11.Arm64.Open
    - System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
net8.0-windows-Release-arm64-CoreCLR_checked-no_tiered_compilation-Windows.11.Arm64.Open
    - System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
net8.0-windows-Release-arm64-CoreCLR_checked-zapdisable-Windows.11.Arm64.Open
    - System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
net8.0-windows-Release-arm64-CoreCLR_checked-jitstress2-Windows.11.Arm64.Open
    - System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
net8.0-windows-Release-arm64-CoreCLR_checked-jitstress1-Windows.11.Arm64.Open
    - System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages
net8.0-windows-Release-arm64-CoreCLR_checked-jitminopts-Windows.11.Arm64.Open
    - System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages

Error message:

Assert.Equal() Failure
                                 ↓ (pos 42)
Expected: ···c9-a094-de53168c96d0
Actual:   ···c9-a094-de53168c96d0\0
                                 ↑ (pos 42)

Stack trace:

   at System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages() in /_/src/libraries/System.Diagnostics.EventLog/tests/EventLogMessagesTests.cs:line 80
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodInvoker.cs:line 59

Author:	v-wenyuxu
Assignees:	-
Labels:	arch-arm64, os-windows, JitStress, area-CodeGen-coreclr
Milestone:	-

[BruceForstall]

I'm not able to repro this locally. Maybe we should wait until another run or two verifies that it continues to fail.

[BruceForstall]

Well, a separate PR run still failed with these, so these failures look repeatable.

[BruceForstall]

@stephentoub Is #87906 possibly related? It's the only recent change I found with "Event" in the title.
@noahfalk @davmason Any idea what might have changed here?

[stephentoub]

Is #87906 possibly related?

Anything's possible, but this seems very unlikely. It just replaced one singleton instance with another and shouldn't be anywhere near to code that impacts whether something has an extra null terminator.

[davmason]

I am not aware of any changes here. I merged #86850 last night, but it looks like it was merged after this started failing so wouldn't be the issue. Other than that I don't know of any recent changes