[PM-39759] ci: Increase test execution time allowance to 10 seconds#2840
Conversation
… to avoid CI failures.
🤖 Bitwarden Claude Code ReviewOverall Assessment: APPROVE This PR raises the Code Review DetailsNo issues found. The change is limited to two CI workflow files, converging both per-test timeout allowances to a consistent 10-second value. No security, correctness, or breaking-change concerns; line continuations and flag syntax are preserved. |
|
@fedemkr are we sure they're aren't hanging? We didn't have tests taking longer than 1s unless they hanged or we had runner issues, most of them ran bellow 0.5s. We can still try it out. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2840 +/- ##
==========================================
- Coverage 81.19% 78.91% -2.28%
==========================================
Files 1026 1149 +123
Lines 65799 73098 +7299
==========================================
+ Hits 53425 57685 +4260
- Misses 12374 15413 +3039 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
🎟️ Tracking
PM-39759
📔 Objective
It has been seen that 3 seconds is not enough as maximum test execution time allowance as we keep getting failures as "Test exceeded execution time allowance of 3 seconds" on some tests that should be passing.
So we're getting a little more flexible by increasing it to 10 seconds which should cover all or most cases in CI testing as discussed internally.