[SERVER-35472] resmoke.py shouldn't fall back to stderr when logkeeper is unavailable Created: 07/Jun/18 Updated: 29/Oct/23 Resolved: 08/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.7, 4.0.0-rc6, 4.1.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Max Hirschhorn |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | tig-resmoke | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||
| Backport Requested: |
v4.0, v3.6, v3.4, v3.2
|
||||||||||||||||||||||||||||||||
| Sprint: | TIG 2018-06-18 | ||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||
| Linked BF Score: | 25 | ||||||||||||||||||||||||||||||||
| Description |
|
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 |
| Comments |
| Comment by Githook User [ 14/Jul/18 ] |
|
Author: {'username': 'visemet', 'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com'}Message: Instead a special return code of 75 is used to indicate that the log (cherry picked from commit 6ad26a359f7bc366da13d433ed612ff22f69d323) |
| Comment by Githook User [ 13/Jun/18 ] |
|
Author: {'username': 'visemet', 'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com'}Message: Instead a special return code of 75 is used to indicate that the log (cherry picked from commit 6ad26a359f7bc366da13d433ed612ff22f69d323) |
| Comment by Githook User [ 08/Jun/18 ] |
|
Author: {'username': 'visemet', 'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com'}Message: |
| Comment by Yves Duhem [ 08/Jun/18 ] |
|
Reopening this ticket with a suggestion for an improvement over the current solution. To give better signal regarding whether a build is successful or not we could keep the task status as "success" when the tests are successful and only use "setup failure" when there are tests failure. |
| Comment by Githook User [ 08/Jun/18 ] |
|
Author: {'username': 'visemet', 'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com'}Message: Instead a special return code of 75 is used to indicate that the log |