Skip to content

[DO NOT MERGE] Validate firebase connected test flakiness for #1120 - #1123

Closed
mokagio wants to merge 1 commit into
ainfra-3575-does-aztec-android-need-firebase-secrets-firebase-devicefrom
mokagio/aztec-firebase-flakiness-validation
Closed

mokagio wants to merge 1 commit into
ainfra-3575-does-aztec-android-need-firebase-secrets-firebase-devicefrom
mokagio/aztec-firebase-flakiness-validation

Conversation

@mokagio

@mokagio mokagio commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Validation only, do not merge. Stacked on #1120, and closed once CI has answered.

Each PR build runs Connected Tests once, so the ordinary pipeline can't show whether the suite is flaky, as was reported on #1105.

Read the 5 parallel Connected Tests jobs. They are expected to pass, but any failure is a real answer, so please don't fix it here.

Neither Gradle nor Test Lab retries here, so each job failing proves a test failed. Each job's log has to show the full suite ran for a pass to count.

This samples 5 runs on one commit, so a rarer flake can still get through.

Validation only, not to merge: each PR build runs the suite once, which says nothing about flakiness.

---

Generated with the help of Claude Code (Opus 5.5), https://code.claude.com
@mokagio mokagio self-assigned this Nov 3, 2026
@mokagio mokagio closed this Nov 3, 2026
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