[SERVER-40749] Include execution in generated task configuration file name Created: 19/Apr/19 Updated: 29/Oct/23 Resolved: 08/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.11, 4.0.14 |
| 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 | ||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||
| Sprint: | DAG 2019-05-20 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 18 | ||||||||||||
| Story Points: | 1 | ||||||||||||
| Description |
|
The execution number should be included in the generated.task configuration file name. Otherwise, later execution can overwrite the file, but since evergreen will no-op on reruns of generate.task, we don't actually use the new configuration. By including the execution number, we will still have the original configuration for subsequent executions of the sub-tasks. |
| Comments |
| Comment by Githook User [ 16/Dec/19 ] |
|
Author: {'name': 'David Bradford', 'email': 'david.bradford@mongodb.com', 'username': 'dbradf'}Message: (cherry picked from commit be545c5b9b838456b456896959e891ceeab93758) |
| Comment by Githook User [ 08/May/19 ] |
|
Author: {'email': 'david.bradford@mongodb.com', 'name': 'David Bradford', 'username': 'dbradf'}Message: |