Skip to content

[Flaky Test] Un-quarantine 5 flaky tests confirmed green in quarantine pipeline#13979

Merged
ViktorHofer merged 1 commit into
mainfrom
flaky-test/un-quarantine-2026-06-07-008eee2587690770
Jun 8, 2026
Merged

[Flaky Test] Un-quarantine 5 flaky tests confirmed green in quarantine pipeline#13979
ViktorHofer merged 1 commit into
mainfrom
flaky-test/un-quarantine-2026-06-07-008eee2587690770

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Automated un-quarantine of 5 tests that the quarantine pipeline (def 344) has confirmed consistently green on main over multiple builds and days, with zero failures detected.


Microsoft.Build.UnitTests.CreateItem_Tests.LogUnixWarningUponCreateItemExecution — Un-quarantine (6b)

Flaky-test key (automated de-duplication — do not edit):

flaky-test-id: Microsoft.Build.UnitTests.CreateItem_Tests.LogUnixWarningUponCreateItemExecution

Def-344 evidence: 13 distinct green builds, 6 distinct days, legs: Quarantine test logs (Linux), Quarantine test logs (macOS), window: 21 days. Zero failures in def 344 over the same window. Test is [UnixOnlyTheory] so Windows coverage is not required.

Tracked by #8373 (other tests still reference this issue)


Microsoft.Build.UnitTests.CreateItem_Tests.LogUnixWarningUponItemCreationWithDriveEnumeration — Un-quarantine (6b)

Flaky-test key (automated de-duplication — do not edit):

flaky-test-id: Microsoft.Build.UnitTests.CreateItem_Tests.LogUnixWarningUponItemCreationWithDriveEnumeration

Def-344 evidence: 13 distinct green builds, 6 distinct days, legs: Quarantine test logs (Linux), Quarantine test logs (macOS), window: 21 days. Zero failures in def 344 over the same window. Test is [UnixOnlyTheory] so Windows coverage is not required.

Tracked by #8373 (other tests still reference this issue)


Microsoft.Build.UnitTests.ToolTask_Tests.OverrideStdOutImportanceToHigh — Un-quarantine (6b)

Flaky-test key (automated de-duplication — do not edit):

flaky-test-id: Microsoft.Build.UnitTests.ToolTask_Tests.OverrideStdOutImportanceToHigh

Def-344 evidence: 5 distinct green builds, 3 distinct days, legs: Quarantine (Windows), window: 21 days. Zero failures in def 344 over the same window. Quarantine was Windows-scoped (TestPlatforms.Windows) and green evidence is on Windows.

Fixes #13934


Microsoft.Build.UnitTests.ToolTask_Tests.ToolTaskCanChangeCanonicalErrorFormat — Un-quarantine (6b)

Flaky-test key (automated de-duplication — do not edit):

flaky-test-id: Microsoft.Build.UnitTests.ToolTask_Tests.ToolTaskCanChangeCanonicalErrorFormat

Def-344 evidence: 5 distinct green builds, 3 distinct days, legs: Quarantine (Windows), window: 21 days. Zero failures in def 344 over the same window. Quarantine was Windows-scoped (TestPlatforms.Windows) and green evidence is on Windows.

Note: open PR #13956 also modifies this test's body (reverting a sleep workaround) — that PR and this one touch non-overlapping lines and should merge without conflict.

Fixes #13931


Microsoft.Build.UnitTests.BinaryLoggerTests.BinaryLoggerShouldEmbedFilesViaTaskOutput — Un-quarantine (6b)

Flaky-test key (automated de-duplication — do not edit):

flaky-test-id: Microsoft.Build.UnitTests.BinaryLoggerTests.BinaryLoggerShouldEmbedFilesViaTaskOutput

Def-344 evidence: 5 distinct green builds, 3 distinct days, legs: Quarantine test logs (Linux), window: 21 days. Zero failures in def 344 over the same window. Quarantine was Linux-scoped (TestPlatforms.Linux) and green evidence is on Linux.

Fixes #13932


New-flake triage note

The main-pipeline scan (ToolTaskCanChangeCanonicalErrorFormat, 4 rolling-build failures on May 25–26) was classified as a likely regression (single error hash, no PR sources, clustered in 2 days) per triage Step 3. The test was already quarantined for issue #13931 prior to those failures. No new quarantine action was taken; the test is un-quarantined by this PR based on its subsequent def-344 green record.

Generated by Flaky Test Triage · sonnet46 4.7M ·

Tests have been consistently passing in the quarantine pipeline
(def 344) over multiple days and builds with no failures detected.

- Remove [ActiveIssue] from CreateItem_Tests.LogUnixWarningUponCreateItemExecution
  (issue #8373, 13 distinct builds, 6 days, Linux+macOS)
- Remove [ActiveIssue] from CreateItem_Tests.LogUnixWarningUponItemCreationWithDriveEnumeration
  (issue #8373, 13 distinct builds, 6 days, Linux+macOS)
- Remove [ActiveIssue] from ToolTask_Tests.OverrideStdOutImportanceToHigh
  (issue #13934, 5 distinct builds, 3 days, Windows)
- Remove [ActiveIssue] from ToolTask_Tests.ToolTaskCanChangeCanonicalErrorFormat
  (issue #13931, 5 distinct builds, 3 days, Windows)
- Remove [ActiveIssue] from BinaryLoggerTests.BinaryLoggerShouldEmbedFilesViaTaskOutput
  (issue #13932, 5 distinct builds, 3 days, Linux)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions github-actions Bot added the flaky-test Tests that have failed but passed on rerun. label Jun 7, 2026
@ViktorHofer
ViktorHofer merged commit 2e5169c into main Jun 8, 2026
14 checks passed
@ViktorHofer
ViktorHofer deleted the flaky-test/un-quarantine-2026-06-07-008eee2587690770 branch June 8, 2026 08:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

flaky-test Tests that have failed but passed on rerun.

Projects

None yet

1 participant