Repository navigation
ci(ios-integration): run device tests group by group, not the whole file in one process - #80
Merged
Merged
Conversation
…ile in one process The Integration (iOS Simulator) job has failed or timed out on every main push since at least May 2026. It was continue-on-error, so nobody noticed. The code is fine: all 24 groups pass on an iOS simulator when run one at a time (about 17 min locally). Only one 4000+ line file running in a single process kept stalling, the same failure mode already known from the Android device runs. - Loop over the group() names and run each with --plain-name. - Report every failing group, not just the first. - Raise the job timeout from 40 to 75 min to cover a cold build on each group. - Drop --dart-define=SIMULATOR=true: nothing in the test file reads it.
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.
The Integration (iOS Simulator) job has failed or timed out on every main push since at least May 2026 (
continue-on-error: true, so it never blocked anything, but it also never gave useful signal). Verified on the reruns of the v1.8.2 merge commits: single-process run failed with no diagnostics; the code itself is fine — all 24 groups pass locally on an iOS simulator, ~17 min total.Splits the run into one
flutter test --plain-name "<group>"invocation pergroup()in the file, reports every failing group instead of stopping at the first, and raises the job timeout 40→75 min.Verified on this branch (dispatched run 35830038193)
Completed in ~55 min (vs. hanging/failing on the old single-process run). 17/24 groups fully green. 7/24 have exactly one flaky test each, all the same shape — a 45-60s wait for a background task's completion event timing out, scattered across unrelated worker types (HTTP, image compression, constraints, concurrent tasks). That is CI-runner speed, not a regression: this job is still non-gating, and the failures are the pre-existing flakiness the file already documents.
Also confirms, for the first time in CI (not just locally): the #75
onStoppedhook test passes on a real simulator run: