[ci-scan] Skip ActivityTracking tests on Android (refs #129088)

[github-actions]

Reasoning

The BasicEventSourceTests.ActivityTracking tests consistently fail on Android because the Activity ID remains as all-zeros Guid after EventSource Start/Stop operations. On Android with the Mono runtime, the threading/activity context does not propagate as expected, causing Assert.NotEqual(Guid.Empty, ...) to fail.

The [ActiveIssue] attribute with TestPlatforms.Android is the right fix because it narrows the skip condition to only Android, matching the observed scope exactly. All four affected tests share the same root cause.

Linked KBE: #129088

Match verification (from Step 4.8):

1. Same test/family: yes — BasicEventSourceTests.ActivityTracking.StartStopCreatesActivity and 3 sibling tests
2. Same failure signature: yes — Assert.NotEqual() Failure: Values are equal with Expected Not 00000000-0000-0000-0000-000000000000
3. Same OS: yes — Android (android-arm, android-arm64, android-x64, android-x86)
4. Same architecture: yes — all Android architectures affected

Impact on platforms

• runtime-extra-platforms (def 154) / android-arm Release AllSubsets_Mono / Windows.11.Amd64.Android-armel.Open / exit code 1
• runtime-extra-platforms (def 154) / android-x64 Release AllSubsets_Mono / Windows.11.Amd64.Android-x64.Open / exit code 1
• runtime-extra-platforms (def 154) / android-arm64 Release AllSubsets_Mono / exit code 1
• runtime-extra-platforms (def 154) / android-x86 Release AllSubsets_Mono / exit code 1

Errors log

[FAIL] BasicEventSourceTests.ActivityTracking.StartStopCreatesActivity
Assert.NotEqual() Failure: Values are equal
Expected: Not 00000000-0000-0000-0000-000000000000
Actual:       00000000-0000-0000-0000-000000000000
   at BasicEventSourceTests.ActivityTracking.StartStopCreatesActivity()

[FAIL] BasicEventSourceTests.ActivityTracking.ActivityFlowsAsync
[FAIL] BasicEventSourceTests.ActivityTracking.SetCurrentActivityIdBeforeEventFlowsAsync
[FAIL] BasicEventSourceTests.ActivityTracking.SetCurrentActivityIdAfterEventDoesNotFlowAsync

First build it occurred

• Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1449088
• Finished: 2026-06-04T09:47:08Z
• Occurrences in window: 4+ (builds 1449088, 1450787, 1452386, 1452872)
• Computed within the scanned window; may not be the true origin.

Linked issue

#129088

---

Filed by ci-failure-scan, which scans dnceng-public outer-loop pipelines on main and converts stable failures into KBEs and test-disable PRs. Comment here or on the workflow file to suggest changes; ci-failure-scan-feedback reads in-scope feedback daily and opens (or updates) a PR with prompt edits.

Note

🔒 Integrity filter blocked 3 items

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

• #6287 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #125436 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #105441 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

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 · ● 38.1M · ◷

[dotnet-policy-service]

Tagging subscribers to 'arch-android': @vitek-karas, @simonrozsival, @steveisok, @akoeplinger
See info in area-owners.md if you want to be subscribed.