Commit 1aab538
committed
fix(ci): retry each maestro flow once on failure (both platforms)
Stability re-run 2 hit a different Maestro flake on the 5th-or-so
Android flow: "Enter your email or username" extendedWaitUntil timed
out at 25s after launchApp clearState even though the AuthView's
Welcome header was visible (Android Compose accessibility tree lags
visual render on some boots). We've now fixed three separate timing
flakes; each one was a real defect that needed a real fix, but the
underlying pattern is that any individual maestro test invocation has
a non-trivial chance of losing a single-shot timing race on the CI
emulator.
Maestro doesn't expose a --retries flag in the version we ship. Wrap
the per-flow xargs invocation in a 2-attempt retry loop via
`xargs -I FLOW bash -c '...'`: first failure forces-stop the app,
sleeps 10s, retries; second consecutive failure is a real failure
and propagates the non-zero. Catches single-shot timing flakes
without masking genuine regressions (a real bug fails both attempts).
Applied symmetrically on iOS and Android.1 parent 293598f commit 1aab538
1 file changed
Lines changed: 20 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
586 | 586 | | |
587 | 587 | | |
588 | 588 | | |
589 | | - | |
| 589 | + | |
590 | 590 | | |
591 | 591 | | |
592 | 592 | | |
| |||
1001 | 1001 | | |
1002 | 1002 | | |
1003 | 1003 | | |
1004 | | - | |
1005 | | - | |
1006 | | - | |
1007 | | - | |
| 1004 | + | |
| 1005 | + | |
| 1006 | + | |
| 1007 | + | |
| 1008 | + | |
| 1009 | + | |
| 1010 | + | |
| 1011 | + | |
| 1012 | + | |
| 1013 | + | |
| 1014 | + | |
| 1015 | + | |
| 1016 | + | |
| 1017 | + | |
| 1018 | + | |
| 1019 | + | |
| 1020 | + | |
| 1021 | + | |
| 1022 | + | |
1008 | 1023 | | |
1009 | 1024 | | |
1010 | 1025 | | |
| |||
0 commit comments