[PM-36946] ci: Increase per-test timeout from 1s to 2s#2623
Conversation
Parallelized Swift Testing tests can exceed 1s under system load from parallelization itself, causing spurious CI failures. 2s gives headroom without masking genuinely slow tests.
🤖 Bitwarden Claude Code ReviewOverall Assessment: APPROVE This PR raises the xcodebuild Code Review DetailsNo findings. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2623 +/- ##
==========================================
- Coverage 87.30% 86.23% -1.07%
==========================================
Files 1900 2128 +228
Lines 169245 184231 +14986
==========================================
+ Hits 147760 158874 +11114
- Misses 21485 25357 +3872 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-36946
📔 Objective
Increases the
-maximum-test-execution-time-allowancexcodebuild flag from 1 second to 2 seconds in bothtest.ymlandtest-bwa.yml.Parallelized Swift Testing tests can exceed the 1s limit under system load caused by the parallelization itself, resulting in spurious CI failures. Raising the limit to 2s gives those tests headroom without masking genuinely slow tests. Parallelization is a net win for overall suite speed, so the right fix is a slightly looser timeout rather than reverting parallelization.