[test-quarantine] Re-quarantine WebWorkerTemplateE2ETest (CanInvokeMethods, HandlesErrors, CanDisposeWorker)#66148
Closed
github-actions[bot] wants to merge 2 commits intomainfrom
Closed
Conversation
…rs, CanDisposeWorker) These tests were recently unquarantined in #66072 (issue #66035) but have already failed again (build 1342501). Re-quarantining to avoid CI disruption while the underlying flakiness is investigated. Associated issue: #aw_webwrk1 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
github-actions
Bot
added
test-failure
needs-area-label
wtgodbe
approved these changes
Apr 4, 2026
Member
|
CC @ilonatommy since you recently unquarantined these & added diagnostics - the failing build was https://dev.azure.com/dnceng-public/public/_build/results?buildId=1342501&view=results. Let me know if we should hold off on merging this |
Member
|
Oh, never mind, that build was from before the tests were unquarantined in the first place. I'm going to close this & update the workflow. |
wtgodbe
added a commit
that referenced
this pull request
Apr 6, 2026
The Case B re-quarantine logic was counting failures from before the unquarantine commit was merged. This led to tests being unnecessarily re-quarantined based on stale failure data (e.g., PR #66148 re-quarantined tests based on a failure from March 18, but the unquarantine PR #66072 wasn't merged until March 30). Updated to explicitly require that only failures occurring after the unquarantine merge date are considered. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
wtgodbe
added a commit
that referenced
this pull request
Apr 6, 2026
The Case B re-quarantine logic was counting failures from before the unquarantine commit was merged. This led to tests being unnecessarily re-quarantined based on stale failure data (e.g., PR #66148 re-quarantined tests based on a failure from March 18, but the unquarantine PR #66072 wasn't merged until March 30). Updated to explicitly require that only failures occurring after the unquarantine merge date are considered. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
wtgodbe
added a commit
that referenced
this pull request
Apr 6, 2026
The Case B re-quarantine logic was counting failures from before the unquarantine commit was merged. This led to tests being unnecessarily re-quarantined based on stale failure data (e.g., PR #66148 re-quarantined tests based on a failure from March 18, but the unquarantine PR #66072 wasn't merged until March 30). Updated to explicitly require that only failures occurring after the unquarantine merge date are considered. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Member
wtgodbe
added a commit
that referenced
this pull request
Apr 6, 2026
…66174) * Fix re-quarantine criteria to only count post-unquarantine failures The Case B re-quarantine logic was counting failures from before the unquarantine commit was merged. This led to tests being unnecessarily re-quarantined based on stale failure data (e.g., PR #66148 re-quarantined tests based on a failure from March 18, but the unquarantine PR #66072 wasn't merged until March 30). Updated to explicitly require that only failures occurring after the unquarantine merge date are considered. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update .github/workflows/test-quarantine.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Re-quarantines 3 flaky Blazor template E2E tests that were recently unquarantined in #66072 (issue #66138) but have already failed again (build 1342501).
Tests
BlazorTemplates.Tests.WebWorkerTemplateE2ETest.WebWorkerTemplate_CanInvokeMethodsBlazorTemplates.Tests.WebWorkerTemplateE2ETest.WebWorkerTemplate_HandlesErrorsBlazorTemplates.Tests.WebWorkerTemplateE2ETest.WebWorkerTemplate_CanDisposeWorkerAssociated issue: #66138
Note
🔒 Integrity filter blocked 12 items
The following items were blocked because they don't meet the GitHub integrity level.
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter: