[SERVER-38818] Better handle dependencies between generated tasks Created: 03/Jan/19 Updated: 29/Oct/23 Resolved: 08/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.6, 4.1.7 |
| Type: | Improvement | 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 | ||||
| Backport Requested: |
v4.0
|
||||
| Sprint: | DAG 2019-01-14 | ||||
| Participants: | |||||
| Story Points: | 3 | ||||
| Description |
|
With generated tasks, dependencies between tasks gets complicated. The dependencies should exist on the generator tasks and when generating a task should query the evergreen api to determine which dependent tasks were generated and add all of them as dependencies on the tasks being created. |
| Comments |
| Comment by Githook User [ 11/Jan/19 ] |
|
Author: {'username': 'dbradf', 'email': 'david.bradford@mongodb.com', 'name': 'David Bradford'}Message: (cherry picked from commit 00728fb39267f5ca7c6bdc3bb69d2e445b5c3c29) |
| Comment by Githook User [ 08/Jan/19 ] |
|
Author: {'username': 'dbradf', 'email': 'david.bradford@mongodb.com', 'name': 'David Bradford'}Message: |