ci: split module tests into separate job to prevent shard 0 timeouts#655
ci: split module tests into separate job to prevent shard 0 timeouts#655torlando-tech merged 2 commits intomainfrom
Conversation
Shard 0/4 was running both app sharded tests AND :reticulum/:data module tests, making it ~12min vs ~9-10min for other shards. With a 15min timeout this caused intermittent timeout failures on slow CI runners. Moves :reticulum and :data tests into a new `module-tests` job that runs in parallel with the app test shards. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Greptile SummaryThis PR splits
Confidence Score: 4/5
Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A([validate-wrapper]) --> D
B([lint]) --> D
A --> E
B --> E
A --> F
B --> F
A --> G
B --> G
D["kotlin-tests\n(4 shards × :app tests)"]
E["module-tests\n(:reticulum + :data tests)"]
F["instrumented-tests"]
G["other jobs\n(threading-audit, proguard, python-tests)"]
D --> H
E --> H
F --> H
G --> H
H(["ci-passed\n✅ CI Passed — APK Ready"])
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
…ests job Copies the Clean AIDL, Clean JaCoCo, and Cache Robolectric steps from kotlin-tests into module-tests to prevent stale cache issues and avoid re-downloading Robolectric SDKs on every run. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Summary
:reticulumand:datamodule tests out of Kotlin test shard 0 into a newmodule-testsjobci-passedgateTest plan
Module Tests (reticulum + data)job passesci-passedgate correctly depends on the new job🤖 Generated with Claude Code