Capture settings opening failure events - #13892
Draft
JordanNoone wants to merge 1 commit into
Draft
JordanNoone wants to merge 1 commit into
JordanNoone wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Sep 15, 2026
Contributor
Author
|
Final TAB diagnosis for this head:
No additional rerun was started. The remaining real failure stays owned by #13900. |
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.
Record delivered pointer/click events, URL and file state, focus changes, and dialog mount/removal when the user-reset test cannot open Settings. Print the capture in the failing attempt's log and attach it while preserving the original five-second assertion and error.
This improves evidence for #13843; it does not fix the flake. Local browser controls distinguish a prevented click from a transient dialog and preserve both expected assertion failures. The reset test passed on its first native Ubuntu attempt (8.9s) at
122b92675daffcb46930a3d940f1088d3aef0d74in shard 8; two other tests in that shard needed retries. Full CI is blocked by 21 terminal Engine service/connection failures across the three Rust shards.