Skip to content

test(browser): give real-browser tests time on busy CI runners - #164

Merged
httpsphl merged 1 commit into
mainfrom
test/browser-approval-wait
Oct 4, 2026
Merged

httpsphl merged 1 commit into
mainfrom
test/browser-approval-wait

Conversation

@httpsphl

@httpsphl httpsphl commented Oct 4, 2026

Copy link
Copy Markdown
Owner

Two flaky failures of the real-browser tests on CI, unrelated to the PRs they hit:

  • Ubuntu (feat(routines): bots change and delete their own routines, with the owner's ok #161's run): words_made_of_one_element_per_letter_keep_their_spaces got "The owner did not answer about 127.0.0.1 in time": the site request expired after the tests' 3 s approval wait while Chromium was slow to ask.
  • macOS (main, earlier today): new_tabs_and_dialogs_reach_the_bot_and_the_owner_watches saw the new tab still without its address after 5 s.

Changes (tests only):

  • TestDaemon::start_supervised_patient(): approvals wait 30 s. The browser tests' setup() uses it; tests about expiry keep the 3 s daemon.
  • The new-tab wait goes from 5 s to 20 s. Both checks stop as soon as what they wait for arrives, so a healthy run is not slower.

Test plan

  • cargo test -p botloftd (the four browser test files locally with Edge)
  • CI green on Ubuntu, Windows and macOS

Two flakes on CI: a site request expired after the tests' 3 s approval
wait on Ubuntu, and a new tab's address arrived after 5 s on macOS. The
browser tests now run on a daemon whose approvals wait 30 s, and the new
tab gets 20 s; both checks end as soon as what they wait for comes.
@httpsphl
httpsphl enabled auto-merge October 4, 2026 19:33
@httpsphl
httpsphl merged commit 29f45ff into main Oct 4, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant