Skip to content

test(windows-e2e): don't fail on a wait dialog that is still closing - #327

Merged
fylorn merged 1 commit into
devfrom
fix/e2e-wait-dialog-race
Oct 12, 2026
Merged

fylorn merged 1 commit into
devfrom
fix/e2e-wait-dialog-race

Conversation

@fylorn

@fylorn fylorn commented Oct 12, 2026

Copy link
Copy Markdown
Contributor

The Windows end-to-end check in the release pipeline failed once for 2026.10.17: the first copy exited quickly, and the second copy's wait dialog was still closing (only its title left) when Wait-Ready scanned for dialogs, so it was reported as an unexpected dialog. The app itself behaved correctly; a rerun of the job passes.

Wait-Ready now looks again two seconds after it first sees a dialog and fails only if one is still there.

This script only runs in the release and rehearse/** pipelines, so it will be exercised by the next release.

🤖 Generated with Claude Code

…ing it unexpected

When the running copy exits quickly, the second copy's wait dialog can still
be closing, with only its title left, when Wait-Ready looks for dialogs; the
release run for 2026.10.17 failed on that once. Look again after two seconds
and fail only if a dialog is still there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@fylorn
fylorn merged commit 9ec9f0f into dev Oct 12, 2026
6 checks passed
@fylorn
fylorn deleted the fix/e2e-wait-dialog-race branch October 12, 2026 07:22
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 12, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant