You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[CI] LinkSdk SpecialFolder intermittently reports protected folders as writable #26225
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.
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.
Failure signature
LinkSdk.LinkSdkRegressionTest.SpecialFolderintermittently reports a protected special folder as writable:Confirmed occurrences
bf96da28d2420b4b949ae80f3b8a50caec3b032b7176ce0bfb7c08ff0b983388ffda1fdf7195c0dbFirst 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
readOnlyassertion and unrelated PR change scopes.dotnet/maciosissues by test name, folder names, and assertion text.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.