[ci-scan] Exclude SampleProfilerSampleType from NativeAOT on linux-arm (refs #127937)

[github-actions]

Linked KBE: #127937

Reasoning

The SampleProfilerSampleType test starts an EventPipe session with the Microsoft-DotNETCore-SampleProfiler provider and waits for ThreadSample events emitted during the "event generating action". On linux-arm NativeAOT, the SampleProfiler thread-sampling loop never produces events, so the test hangs indefinitely at "Starting event generating action..." until the Helix work item is killed by the 3600-second timeout (exit code 137).

This is a NativeAOT-specific behavior difference on linux-arm: the SampleProfiler does not fire correctly under NativeAOT in this configuration. Marking the test NativeAotIncompatible removes it from the NativeAOT outer-loop build, silencing the timeout. The test continues to run on CoreCLR.

Impact on platforms

• runtime-nativeaot-outerloop (def 265) — linux-arm Checked NativeAOT_Pri1 — tracing/eventpipe/eventsvalidation/SampleProfilerSampleType — Helix work item timeout after 3600000 ms
• Queue: (Debian.13.Arm32)AzureLinux.3.Arm64.Open

All 7 scanned builds of pipeline 265 that are checked show this failure.

Errors log

[xUnit.net 00:59:59.28]   Tracing.Tests.SampleProfilerSampleType.SampleProfilerSampleType.TestEntryPoint [TIMEOUT]
[xUnit.net 00:59:59.28] Total: 1 test, 1 failed
WorkItem SampleProfilerSampleType/SampleProfilerSampleType.sh Timed Out
```

```
Starting event generating action...
[hung — no further output; work item killed at 3600s]

First build it occurred

First observed within the scanned window: build 1403893 (earliest of 7+ affected builds in the window). This is computed within the scanned window and may not be the true origin.

Build link: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1403893

Linked issue

KBE: #127937

Note

This PR was opened by the CI Outer-Loop Failure Scanner (automated workflow).

Note

🔒 Integrity filter blocked 21 items

The following items were blocked because they don't meet the GitHub integrity level.

• #124716 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #68230 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #126154 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #70517 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #122521 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #69953 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #48389 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #1550 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #61397 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #127153 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #85603 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #57892 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #127774 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #124045 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #105974 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #93308 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• ... and 5 more items

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by CI Outer-Loop Failure Scanner · ● 8M · ◷

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

[lateralusX]

#127937 tracks this issue.

[MichalStrehovsky]

Are you okay disabling on native AOT everywhere even though this was only ever observed on arm32 runs? (This test likely has problems if JitStress runs are able to hit a 60 minute timeout, but up until very recently nobody cared about Pri1 runs with CoreCLR, they have not been green since .NET 9. It's also likely this is not even AOT specific, but I do care about native AOT outerloops and we do have them green sometimes, which is why I filed a bug on the native AOT occurence.)

[lateralusX]

If we pass on all other platforms, then I believe we could limit the exclude range to failing platforms/architectures, so if its only linux-arm I guess we could do something along:

<CLRTestTargetUnsupported Condition="'$(TargetOS)' == 'linux' and '$(TargetArchitecture)' == 'arm'">true</CLRTestTargetUnsupported>

If that doesn't work for the NAOT pipeline we could add the same condition to the NativeAotIncompatible property already used in this PR.

[MichalStrehovsky]

I'm not able to get the Known issue validation thing to collect the information in #127937. So we don't know if it's specific to arm or native AOT or whether it was an infrastructure hiccup.