BasicEventSourceTests.TestsManifestGeneration.Test_EventSource_EtwManifestGeneration is failing in CI

[tarekgh]

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1091361
Build error leg or test failing: BasicEventSourceTests.TestsManifestGeneration.Test_EventSource_EtwManifestGeneration
Pull request: #116534

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": ["BasicEventSourceTests.TestsManifestGeneration.Test_EventSource_EtwManifestGeneration", "Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Remote process failed with an unhandled exception."],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1091361
Error message validated: [BasicEventSourceTests.TestsManifestGeneration.Test_EventSource_EtwManifestGeneration Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Remote process failed with an unhandled exception.]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/10/2025 9:17:28 PM UTC

Report

Build	Definition	Test	Pull Request
2929174	dotnet-runtime	BasicEventSourceTests.TestsManifestGeneration.Test_EventSource_EtwManifestGeneration	#59173
1331423	dotnet/runtime	BasicEventSourceTests.TestsManifestGeneration.Test_EventSource_EtwManifestGeneration	#125466
1331318	dotnet/runtime	BasicEventSourceTests.TestsManifestGeneration.Test_EventSource_EtwManifestGeneration	#124544
1320253	dotnet/runtime	BasicEventSourceTests.TestsManifestGeneration.Test_EventSource_EtwManifestGeneration	#124544
1314909	dotnet/runtime	BasicEventSourceTests.TestsManifestGeneration.Test_EventSource_EtwManifestGeneration	#123245

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	1	5

[dotnet-policy-service]

Tagging subscribers to this area: @tarekgh, @tommcdon, @steveisok, @pjanotti
See info in area-owners.md if you want to be subscribed.

[danmoseley]

Note

This analysis was generated with assistance from GitHub Copilot.

Root Cause: Failures are exclusively from release/8.0

All recent failures tracked by this issue (and the related #88027 for the Rollover variant) are coming from the release/8.0 branch. The PRs in the Known Build Error hit tables confirm this — they are all release/8.0 servicing PRs (dependency updates, staging merges, etc.).

Why release/8.0 is different

Between Nov 2023 and Jul 2024, six PRs landed on main to address this test:

PR	Date	What it did
#95389	Nov 2023	[ActiveIssue] on x86 only
#96816	Jan 2024	Replaced [ActiveIssue] with [SkipOnCoreClr] (re-enabled on non-stress)
#96950	Jan 2024	Eliminated the double-RemoteExecutor pattern, added retry logic, moved ETW setup before child launch
#97115	Jan 2024	Removed timeouts, reduced event count 100→50, added explicit WaitForExit
#97258	Jan 2024	Re-added [ActiveIssue] on x86
#105069	Jul 2024	Unconditional [ActiveIssue] disable (current state on main)

None of these were backported to release/8.0. The test on that branch still has:

• No [ActiveIssue] attribute
• No [SkipOnCoreClr] attribute
• The old double-RemoteExecutor pattern (process spawns RemoteExecutor which spawns another RemoteExecutor)
• Old hardcoded Thread.Sleep + retry loops

Current state by branch

Branch	[ActiveIssue]?	Test reworked?	Failing?
release/8.0	❌	❌	Yes
release/9.0	✅	✅	No (disabled)
release/10.0	✅	✅	No (disabled)
main	✅	✅	No (disabled)

Recommendation

Backport the [ActiveIssue] attribute to release/8.0 to silence the CI noise. .NET 8 EOL is November 2026, so backporting the full test rework isn't worth the risk — just disable it.

This issue and #88027 track the same root cause (same test, Rollover vs non-Rollover variant). Both will be resolved by the same backport.

[danmoseley]

I've updated #88027 to track this as well, so I'll close this. Still need the PR to backport to 8.0