Skip to content

CI stability: drop flutter test -v, retry the iOS warm-up, longer Cronet test waits - #3

Merged
gartnera merged 3 commits into
mainfrom
claude/gifted-carson-kzx7k9
Nov 9, 2026
Merged

gartnera merged 3 commits into
mainfrom
claude/gifted-carson-kzx7k9

Conversation

@gartnera

@gartnera gartnera commented Nov 9, 2026 •

Copy link
Copy Markdown
Member

Drop -v from the Dart integration steps

Both Dart integration steps in ci.yaml (iOS and Android) still passed -v to flutter test. Both were marked DEBUG and were added to diagnose flutter test launching the app and then never connecting to it.

Verbose output puts the whole Xcode/Gradle build and the app's Info.plist into every job log, and buries the test results.

Why they can go now:

Retry the iOS warm-up call

In run 42689216883 on main, the single warm-up call timed out after 10 s and failed setUpAll, so none of the test cases ran.

The simulator's trustd log shows why:

  • 20:12:13: trustd began updating its pinning database from version 118 to 131. The update came from a PKITrustSupplementals trust-data download on the freshly booted simulator.
  • From then on: every certificate evaluation, Apple's own and the app's, retried a locked SQLite database (sqlite busy/locked). That was still going when the log ended at 20:15:34, more than 3 minutes later.
  • Earlier runs: two earlier runs that recorded trustd show no such update and no lock.

setUpAll now makes up to three 8 s attempts. Each attempt uses a fresh client, and a deadline cancels the stalled call. Each outcome is logged.

This rides out a shorter stall. It would not have saved that run, where the lock outlasted the whole suite.

Longer waits in CronetBridgeTest

In run 42691768445, writesBeforeTheStreamIsReadyAreSentOnceItIs failed with no events after its 3 s wait. What the logs show:

  • The request arrived late: the server received it about 3 s after the call was opened, just as the wait gave up.
  • Fresh connection per case: each case builds a new Cronet engine, so a new TCP+TLS connection through the emulator to the host.
  • Not DNS, not CPU: DNS was answered from cache in 3 ms, and the test process was idle the whole time.

3 s matches two lost connection attempts retried after 1 s and 2 s, but the logs can't confirm that. The waits are now 10 s, as the Dart cases allow.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BqmpXW1H7XRFuEgBWW3ppW

Both Dart steps ran flutter test verbose, marked DEBUG, to see what it waited on when it launched the app and never
connected. iOS's cause was a flutter_tools race, now patched in the workflow; the Android hang hasn't recurred, and
logcat is still recorded as an artifact. Verbose output put the whole Xcode/Gradle build and the app's Info.plist in
every job log, burying the test results.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BqmpXW1H7XRFuEgBWW3ppW
In run 42689216883 on main the single warm-up call timed out after 10 s and failed setUpAll, so none of the cases ran.
trustd had stalled every certificate check: at 20:12:13 it began updating its pinning database (version 118 to 131,
from a PKITrustSupplementals trust data update it downloaded on the freshly booted simulator), and its other
evaluations then retried a locked SQLite database for the rest of the run.

setUpAll now makes up to three 8 s attempts, each on a fresh client whose call a deadline cancels, and logs each
outcome. That rides out a shorter stall; it would not have saved that run, where the lock outlasted the suite.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BqmpXW1H7XRFuEgBWW3ppW
@gartnera gartnera changed the title Run the Dart integration suites without flutter test's -v Drop flutter test -v from CI; retry the iOS suite's warm-up call Nov 9, 2026
In run 42691768445 writesBeforeTheStreamIsReadyAreSentOnceItIs failed with no events for its call after 3 s. The
server received the call's request about 3 s after it was opened, just as the wait gave up: each case builds a fresh
Cronet engine and so a fresh TCP+TLS connection to the host through the emulator, and this one took that long to
come up. DNS was answered from cache in 3 ms and the test process was idle meanwhile. 3 s matches two lost-SYN
retransmissions (1 s + 2 s), though the logs can't confirm the packet loss.

10 s, as the Dart cases allow, still fails a real hang quickly.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BqmpXW1H7XRFuEgBWW3ppW
@gartnera gartnera changed the title Drop flutter test -v from CI; retry the iOS suite's warm-up call CI stability: drop flutter test -v, retry the iOS warm-up, longer Cronet test waits Nov 9, 2026
@gartnera
gartnera enabled auto-merge (squash) November 9, 2026 20:44
@gartnera
gartnera merged commit 4058c0a into main Nov 9, 2026
6 checks passed
@gartnera
gartnera deleted the claude/gifted-carson-kzx7k9 branch November 9, 2026 20:44
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.

2 participants