Repository navigation
tracing/runtimeeventsource/nativeruntimeeventsource/nativeruntimeeventsource failing in CI #90605
Description
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=374041
Build error leg or test failing: tracing/runtimeeventsource/nativeruntimeeventsource/nativeruntimeeventsource.sh
Pull request: #90553
Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorMessage": "System.Exception: Condition 'listener.EventCount > 0' is not true",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Failure:
Unhandled Exception:
System.Exception: Condition 'listener.EventCount > 0' is not true
at Tracing.Tests.NativeRuntimeEventSourceTest.Assert2.True(String name, Boolean condition)
at Tracing.Tests.NativeRuntimeEventSourceTest.Main()
[ERROR] FATAL UNHANDLED EXCEPTION: System.Exception: Condition 'listener.EventCount > 0' is not true
at Tracing.Tests.NativeRuntimeEventSourceTest.Assert2.True(String name, Boolean condition)
at Tracing.Tests.NativeRuntimeEventSourceTest.Main()
Return code: 1
Raw output file: /root/helix/work/workitem/uploads/Reports/tracing.runtimeeventsource/nativeruntimeeventsource/nativeruntimeeventsource.output.txt
Raw output:
BEGIN EXECUTION
/root/helix/work/correlation/corerun -p System.Reflection.Metadata.MetadataUpdater.IsSupported=false -p System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true nativeruntimeeventsource.dll ''
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=374041
Error message validated: System.Exception: Condition 'listener.EventCount > 0' is not true
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 8/15/2023 4:15:41 PM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 2 | 17 |
Activity
AaronRobinsonMSFT commentedon Aug 19, 2023
This is actually failing in mono, not coreclr. The leg is
AaronRobinsonMSFT commentedon Aug 19, 2023
@tommcdon Since this looks like a mono issue I am marking it untriaged and removing @davmason. Apologies if I have overstepped.
4 remaining items
SamMonoRT commentedon Aug 28, 2023
@steveisok - @fanyang-mono brought this to my attention. A PR to disable the test in main and release\8.0 will be stood up soon to enable cleaner CI, and we can work on identifying the root cause of the failures.
SakeTao commentedon Aug 22, 2025
Failed in: runtime-coreclr outerloop 20250821.7
Failed tests:
Error message:
Stack trace:
SakeTao commentedon Dec 10, 2025
Failed in: runtime-coreclr outerloop 20251209.5
Failed tests:
Error message:
Stack trace:
SakeTao commentedon Dec 17, 2025
Failed in: runtime-coreclr outerloop 20251216.2
Failed tests:
Error message:
Stack trace:
SakeTao commentedon Dec 18, 2025
Failed in: runtime-coreclr outerloop 20251217.2
Failed tests:
Error message:
Stack trace:
SakeTao commentedon Dec 19, 2025
Failed in: runtime-coreclr outerloop 20251218.2
Failed tests:
Error message:
Stack trace:
VincentBu commentedon Apr 14, 2026
Failed in: runtime-coreclr r2r 20260412.1
Failed tests:
Error message:
Stack trace:
MichalStrehovsky commentedon Jul 21, 2026
@dotnet/area-tracing-coreclr FYI - this issue is marked as area-Tracing-mono and is in the "don't care" Future milestone but looks like quite a bit of the failures are on top of CoreCLR, not Mono (see previous comments and e.g. the failure from last week in the Build analysis table). I clicked on this issue out of curiosity because it was failing in my PR.