…8.0 (#126008)

main PR #105069

# Description

`Test_EventSource_EtwManifestGeneration` and
`Test_EventSource_EtwManifestGenerationRollover` are consistently flaky
on `release/8.0` due to the old double-`RemoteExecutor` pattern and
timing-based retry loops. These tests have been unconditionally disabled
via `[ActiveIssue]` on `main`, `release/9.0`, and `release/10.0`, but
the attribute was never backported to `release/8.0`.

Adds `[ActiveIssue("https://github.com/dotnet/runtime/issues/88027")]`
to both tests in `TestsManifestGeneration.Etw.cs`:

```csharp
[ConditionalFact(nameof(IsProcessElevatedAndNotWindowsNanoServerAndRemoteExecutorSupported))]
[ActiveIssue("#88027")]
public void Test_EventSource_EtwManifestGeneration()

[ConditionalFact(nameof(IsProcessElevatedAndNotWindowsNanoServerAndRemoteExecutorSupported))]
[ActiveIssue("#88027")]
public void Test_EventSource_EtwManifestGenerationRollover()
```

This PR targets the `release/8.0` branch. A clean branch
(`copilot/fix-etw-test-8.0`) based directly on `release/8.0` is
available with just this 2-line fix.

# Customer Impact

Ongoing CI noise on every `release/8.0` servicing PR. No customer-facing
behavioral change.

# Regression

No — this is a pre-existing flaky test, not a regression introduced in
the latest release.

# Testing

No new tests. The fix is to skip tests that are already skipped on all
newer branches. Verified `[ActiveIssue]` attribute matches the form used
on `main`/`release/9.0`/`release/10.0`.

# Risk

Minimal. Two-line change disabling already-flaky tests. No production
code touched. Identical pattern already proven stable on three other
branches.

# Package authoring signed off?

N/A — test-only change, no NuGet packages affected.

<!-- START COPILOT ORIGINAL PROMPT -->



<details>

<summary>Original prompt</summary>


----

*This section details on the original issue you should resolve*


<issue_title>BasicEventSourceTests.TestsManifestGeneration.Test_EventSource_EtwManifestGeneration
is failing in CI</issue_title>
<issue_description>## 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 template  -->
## Error Message

Fill the error message using [step by step known issues
guidance](https://github.com/dotnet/arcade/blob/main/Documentation/Projects/Build%20Analysis/KnownIssueJsonStepByStep.md).

<!-- Use ErrorMessage for String.Contains matches. Use ErrorPattern for
regex matches (single line/no backtracking). Set BuildRetry to `true` to
retry builds with this error. Set ExcludeConsoleLog to `true` to skip
helix logs analysis. -->

```json
{
  "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 start -->
 ### 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
<!-- Known issue validation end -->
<!--Known issue error report start -->

### Report

|Build|Definition|Test|Pull Request|
|---|---|---|---|

|[2929174](https://dev.azure.com/dnceng/internal/_build/results?buildId=2929174)|dotnet-runtime|[BasicEventSourceTests.TestsManifestGeneration.Test_EventSource_EtwManifestGeneration](https://dev.azure.com/dnceng//internal/_build/results?buildId=2929174&view=ms.vss-test-web.build-test-results-tab&runId=56585111&resultId=159157)|[#59173](https://dev.azure.com/dnceng/internal/_git/dotnet-runtime/pullrequest/59173)|

|[1331423](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1331423)|dotnet/runtime|[BasicEventSourceTests.TestsManifestGeneration.Test_EventSource_EtwManifestGeneration](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1331423&view=ms.vss-test-web.build-test-results-tab&runId=37189800&resultId=168777)|dotnet/runtime#125466|

|[1331318](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1331318)|dotnet/runtime|[BasicEventSourceTests.TestsManifestGeneration.Test_EventSource_EtwManifestGeneration](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1331318&view=ms.vss-test-web.build-test-results-tab&runId=37187004&resultId=170098)|dotnet/runtime#124544|

|[1320253](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1320253)|dotnet/runtime|[BasicEventSourceTests.TestsManifestGeneration.Test_EventSource_EtwManifestGeneration](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1320253&view=ms.vss-test-web.build-test-results-tab&runId=36862006&resultId=160082)|dotnet/runtime#124544|

|[1314909](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1314909)|dotnet/runtime|[BasicEventSourceTests.TestsManifestGeneration.Test_EventSource_EtwManifestGeneration](https://dev.azure.com/dnceng-public/public/_build/results?buildId=1314909&view=ms.vss-test-web.build-test-results-tab&runId=36716758&resultId=159027)|dotnet/runtime#123245|
#### Summary
|24-Hour Hit Count|7-Day Hit Count|1-Month Count|
|---|---|---|
|0|1|5|
<!--Known issue error report end --></issue_description>

<agent_instructions>Disable both of these in the 8.0 branch (ONLY) using
` [ActiveIssue("https://github.com/dotnet/runtime/issues/88027")`
They already have that disabling in 9, 10, and
main.</agent_instructions>

## Comments on the Issue (you are @copilot in this section)

<comments>
<comment_new><author>@danmoseley</author><body>
> [!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 &#8212; 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...

</details>



<!-- START COPILOT CODING AGENT SUFFIX -->

- Fixes #117520

<!-- START COPILOT CODING AGENT TIPS -->
---

⚡ Quickly spin up Copilot coding agent tasks from anywhere on your macOS
or Windows machine with [Raycast](https://gh.io/cca-raycast-docs).

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: danmoseley <6385855+danmoseley@users.noreply.github.com>

> [!NOTE]
> This PR was AI/Copilot-generated.

This fixes the release/8.0 Markdownlint workflow failure caused by
running the current `markdownlint-cli` on the old Node 16 runtime.

- update `actions/checkout` to `@v6`
- update `actions/setup-node` to `@v6`
- switch the workflow to `node-version: 'lts/*'`\n\nThis restores
markdownlint for PRs like #126528 where the markdown files themselves
were already clean.

---------

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>