-
Type:
Improvement
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
DevProd Build
-
Build OnDeck
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We use retry on timeout mechanism to avoid dealing with transient network issues or other similar transient issues that pop in CI and reduce BF triage workload. We currently have no timeout/retry mechanism for no remote exec builds, so they still get it with these issue occasionally. Since a retry has very little overhead we should just add a default timeout which will fix the transient issues and worse case add only a few seconds overhead on unnessary restarts.
- is related to
-
SERVER-129794 make evergreen bazel builds (not test) retry in all cases
-
- Closed
-