[SERVER-65141] Handle build variant generation when priority is -1 Created: 31/Mar/22 Updated: 29/Oct/23 Resolved: 01/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Bradford (Inactive) | Assignee: | David Bradford (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | DAG 2022-04-04 | ||||
| Participants: | |||||
| Linked BF Score: | 226 | ||||
| Story Points: | 1 | ||||
| Description |
|
When generating tasks for a build variant, we will update the priority of _gen tasks by 1. However, if the version as a whole has been disabled, the priority could be -1, in which case, we would attempt to set the priority to 0. But due to a bug in evergreen.py, attempting to set a priority of 0 will result in call the evergreen api with an empty body and trigger an exception. We should fix this. |
| Comments |
| Comment by Githook User [ 01/Apr/22 ] |
|
Author: {'name': 'David Bradford', 'email': 'david.bradford@mongodb.com', 'username': 'dbradf'}Message: |