-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Fully Compatible
-
v4.0, v3.6, v3.4, v3.2
-
TIG 2018-06-18
-
25
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
The Evergreen team believes that having resmoke.py fall back to writing the test output to its stderr (and therefore to the "task logs") puts too much pressure on the Evergreen database when logkeeper is unavailable. We would rather discard the test results of an Evergreen task if we fail to record any log messages to the logkeeper rather than try to preserve the test results and record log messages to the Evergreen database.
We can reuse the mechanism from SERVER-32121 to cause the Evergreen task to turn purple should resmoke.py find that logkeeper is unavailable.
- depends on
-
SERVER-32121 resmoke.py should cause the Evergreen task to system fail if the EC2 instance is terminated
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
SERVER-40592 Uncaught exception in resmoke.py job thread due to logkeeper unavailability when tearing down fixture
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-