-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test failure System.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages #88224
Comments
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsFailed in: runtime-coreclr libraries-jitstress 20230629.1 Failed tests:
Error message:
Stack trace:
|
I'm not able to repro this locally. Maybe we should wait until another run or two verifies that it continues to fail. |
Well, a separate PR run still failed with these, so these failures look repeatable. |
@stephentoub Is #87906 possibly related? It's the only recent change I found with "Event" in the title. |
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. |
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 |
This fails consistently in runtime-extra-platforms too: https://runfo.azurewebsites.net/search/tests/?q=started%3A%7E7+definition%3Aruntime-extra-platforms+name%3ASystem.Diagnostics.Tests.EventLogMessagesTests.CanReadAndWriteMessages So doesn't seem like a jitstress issue. Given that it fails in jitminopts, it's also very unlikely to be a JIT issue., so will move this out. |
Tagging subscribers to this area: @tommcdon Issue DetailsFailed in: runtime-coreclr libraries-jitstress 20230629.1 Failed tests:
Error message:
Stack trace:
{
"ErrorMessage": "CanReadAndWriteMessages",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": true
} Known issue validationBuild: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=324820 ReportSummary
|
…eMessages on Windows 11 Fixes blocking status for dotnet#88224
Tagging subscribers to this area: @dotnet/area-system-diagnostics-eventlog Issue DetailsFailed in: runtime-coreclr libraries-jitstress 20230629.1 Failed tests:
Error message:
Stack trace:
{
"ErrorMessage": "CanReadAndWriteMessages",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": true
} Known issue validationBuild: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=324820 ReportSummary
|
The failure appears to only be on Windows 11. I've disabled it there in #88472. |
Failed in: runtime-coreclr libraries-jitstress 20230629.1
Failed tests:
Error message:
Stack trace:
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
Summary
The text was updated successfully, but these errors were encountered: