[test-quarantine] Quarantine BlazorWebJsInitializersTest.InitializersRunsModernCallbacksByDefaultWhenPresent#66283
Closed
github-actions[bot] wants to merge 1 commit intomainfrom
Conversation
…sByDefaultWhenPresent The test has been failing consistently (23+ times) in the components-e2e pipeline (definition 87) on the main branch over the past 30 days. Associated issue: #aw_blzinit1 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Member
|
Don't think it was a flaky test issue, but a real issue that I believe has been fixed. |
wtgodbe
added a commit
that referenced
this pull request
Apr 12, 2026
Check closed (not merged) [test-quarantine] PRs from the past 30 days before creating new quarantine/unquarantine PRs. If a previous PR for the same test was closed by a repo member with a comment explaining why (e.g., test wasn't actually flaky, fix was merged), skip that test for the current run. Motivated by PR #66283 where a quarantine PR was closed because the test failure was a real bug that had already been fixed, not a flaky test. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
wtgodbe
added a commit
that referenced
this pull request
Apr 12, 2026
Check closed (not merged) [test-quarantine] PRs from the past 30 days before creating new quarantine/unquarantine PRs. If a previous PR for the same test was closed by a repo member with a comment explaining why (e.g., test wasn't actually flaky, fix was merged), skip that test for the current run. Motivated by PR #66283 where a quarantine PR was closed because the test failure was a real bug that had already been fixed, not a flaky test. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
wtgodbe
added a commit
that referenced
this pull request
Apr 12, 2026
* Skip tests that were previously rejected for quarantine/unquarantine Check closed (not merged) [test-quarantine] PRs from the past 30 days before creating new quarantine/unquarantine PRs. If a previous PR for the same test was closed by a repo member with a comment explaining why (e.g., test wasn't actually flaky, fix was merged), skip that test for the current run. Motivated by PR #66283 where a quarantine PR was closed because the test failure was a real bug that had already been fixed, not a flaky test. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Specify trusted author_association values for closed PR checks Use explicit author_association values (OWNER, MEMBER, COLLABORATOR, CONTRIBUTOR) instead of vague 'repository member or contributor' wording. CONTRIBUTOR is needed because github-actions[bot] (which runs the quarantine workflow) has that association value. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+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.
Summary
Quarantine
BlazorWebJsInitializersTest.InitializersRunsModernCallbacksByDefaultWhenPresentwhich has been failing consistently in CI.Associated issue: #66282
Failure Details
The test has failed 23+ times on the
mainbranch over the past 30 days in the components-e2e pipeline (definition 87). The failures showAssert.NotEmpty() Failure: Collection was empty— the expected JavaScript initializer callback DOM elements are not present in the browser when the test asserts them.Representative failing builds:
Changes
[QuarantinedTest("https://github.com/dotnet/aspnetcore/issues/#66282")]toInitializersRunsModernCallbacksByDefaultWhenPresentusing Microsoft.AspNetCore.InternalTesting;Note
🔒 Integrity filter blocked 6 items
The following items were blocked because they don't meet the GitHub integrity level.
pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".pull_request_read: 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".pull_request_read: 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: