The spec shares the app's per-minute API rate limiter with every other spec
in the suite, so a late-run burst can answer 429. Its setup treated that as a
hard failure, and a rate-limited bootstrap leaves the shell without its data
and does not recover on its own, so the retries then failed waiting for the
dashboard.
Retry the login and dashboard readiness, the stack creates (only a 429 is
retried; any other status still fails on the first answer) and the post-setup
reload, waiting out the window between attempts. The describe gets a longer
test budget so a saturated minute cannot time the retries out. The app's
rate-limit behavior is unchanged.
Anso
4453ca552e