[test-quarantine] Quarantine VirtualizeTest.Virtualize_ScrollToBottom_SetWhenAtEndWithNewMeasurements#66156
Closed
github-actions[bot] wants to merge 2 commits intomainfrom
Closed
Conversation
…ewMeasurements This test has failed 3 times in the last 30 days (build 1362201). The failure message is 'scrollToBottom should either be called via JS interop or be pending', indicating a timing issue with the JS interop call in the Virtualize component. Associated issue: #aw_vrtzscr 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
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.
Quarantines a flaky Virtualize component unit test that has failed 3 times in the last 30 days (build 1362201, pipeline 83).
Test
Microsoft.AspNetCore.Components.Virtualization.VirtualizeTest.Virtualize_ScrollToBottom_SetWhenAtEndWithNewMeasurementsThe test fails with:
This indicates a timing issue where the
scrollToBottomJS interop call is neither made synchronously nor queued as pending when expected, suggesting a race condition in the Virtualize component's scroll-to-bottom logic when new measurements are applied.Associated issue: #66143
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: