Skip to content

[CI] LinkSdk SpecialFolder intermittently reports protected folders as writable #26225

Description

@dalexsoto

Failure signature

LinkSdk.LinkSdkRegressionTest.SpecialFolder intermittently reports a protected special folder as writable:

Assert.That(readOnly, Is.True)
Expected: True
But was: False

Confirmed occurrences

PR / head Build and job Platform / folder Outcome
#25979 / bf96da28d2420b4b949ae80f3b8a50caec3b032b 14720177 - linker_macos macOS / Desktop The bot reported the folder writable. Simulator-tests attempt 2 was accepted at 22:52 UTC and remains queued.
#26220 / 7176ce0bfb7c08ff0b983388ffda1fdf7195c0db 14721806 - linker_maccatalyst Mac Catalyst / MyDocuments The bot reported the folder writable. The build remains active.

First observed: 2026-07-21 20:02 UTC. Latest observed: 2026-07-22 00:08 UTC. Recurrence: 2 jobs across 2 distinct monitored PRs.

Classification and impact

This is a genuinely flaky environment/test failure, not a source regression. It occurs in unrelated PRs on different Apple platforms, while sibling linker variations pass. The stable signature is the same test and read-only assertion; only the special-folder value differs.

Investigation

  • Inspected TestSummary and HtmlReport artifacts for both failures.
  • Confirmed the exact readOnly assertion and unrelated PR change scopes.
  • Searched open and closed dotnet/macios issues by test name, folder names, and assertion text.
  • Closed issue [dotnet] LinkSdk.LinkSdkRegressionTest.SpecialFolder fails on tvOS #12640 concerns a different tvOS folder-existence/test-order failure, not this read-only mismatch.

Workaround

Rerun failed jobs after confirming mergeability and retry budgets. Do not submit another retry while an equivalent stage attempt is queued or running. Azure artifacts have limited retention.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ci-failureThe issue only affects CIci-postmortemCI post-mortem analysis: flaky tests, infrastructure failures, shared regressionstestsAnything related to tests

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions