Skip to content

[Flaky Test] Microsoft.Build.UnitTests.ToolTask_Tests.ToolTaskCanChangeCanonicalErrorFormat #13949

Closed as not planned

Description

@github-actions

Flaky test: ToolTask_Tests.ToolTaskCanChangeCanonicalErrorFormat

Assembly: Microsoft.Build.Utilities.UnitTests

Evidence

Sample error

Assert.Contains() Failure: Sub-string not found
String:    "C:\Windows\system32\cmd.exe /C type "C:\Users\clou"···
Not found: "CS0168"

Notes

The test fails intermittently on Windows when checking that a canonical error format string appears in the tool's output. This is likely a timing or process-output-buffering race condition.

Fix guidance

Preferred fix: identify the source of nondeterminism (e.g. output buffering, process exit timing) and make a minimal determinism fix in the test.

Fallback: quarantine via [ActiveIssue("https://github.com/dotnet/msbuild/issues/NNNN")] from Microsoft.DotNet.XUnitV3Extensions (namespace Xunit) — not [Fact(Skip=...)].

Generated by Flaky Test Triage and Fix · sonnet46 4.5M · ◷

Activity

  1. ViktorHofer commented on Jun 5, 2026

    @ViktorHofer
    Member

    Duplicate of #13931. This test was filed multiple times because the tracking-issue marker wasn't being written, so consecutive daily detector runs couldn't dedupe. Tracking continues in #13931, which is the issue referenced by the [ActiveIssue] attribute in #13937.

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

    flaky-testTests that have failed but passed on rerun.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions