[SERVER-30565] burn_in_tests.py shouldn't cause compile task to fail Created: 08/Aug/17 Updated: 30/Oct/23 Resolved: 11/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.11, 3.5.12 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Yves Duhem |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v3.4
|
||||||||||||
| Sprint: | TIG 2017-08-21 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
We occasionally experience network connectivity issues with the Evergreen API server while running tasks in Evergreen. This causes burn_in_tests.py to exit with a non-zero return code because of an uncaught connection error.
We should remove the invocation of burn_in_tests.py the "compile" task and instead change the "burn_in_tests" task to run the git.get_project command to clone the mongodb/mongo repository and apply the user's patch if necessary. If we continue use the --noExec invocation of burn_in_tests.py, then we can make this logic in the "compile" task a command of type="system" so that failing to communicate with the Evergreen API server causes the task to turn purple. |
| Comments |
| Comment by Githook User [ 17/Jan/18 ] |
|
Author: {'name': 'Yves Duhem', 'email': 'yves.duhem@mongodb.com', 'username': 'syev'}Message: (cherry picked from commit 7969a3e83d918a9a3ccaae65c6509b1abad4b34e) Also includes the following related fix: |
| Comment by Githook User [ 11/Aug/17 ] |
|
Author: {'name': 'Yves Duhem', 'email': 'yves.duhem@mongodb.com'}Message: |