-
- Downloads
Bug 1666809 - Insert decision task indexes directly via taskluster API rather...
Bug 1666809 - Insert decision task indexes directly via taskluster API rather than index-task, r=taskgraph-reviewers,aki We started using the "backstop" index added by bug 1660506 to determine whether a push should be a backstop based on a time interval. The problem is that this index gets added by an index-task that runs after the decision task has completed. Therefore, if two pushes land at roughly the same time (i.e, the second decision task starts before the first completes), then they can both determine themselves as backstops. This patch gets around the problem by inserting the "backstop" index as early as possible (immediately after resolving parameters), so the chances of this happening become very low. It's still theoretically possible that it could happen again, but we don't need this to be 100% perfect. As long as it is rare, it's good enough. Depends on D91191 Differential Revision: https://phabricator.services.mozilla.com/D91192
Showing
- .taskcluster.yml 1 addition, 0 deletions.taskcluster.yml
- taskcluster/taskgraph/decision.py 17 additions, 1 deletiontaskcluster/taskgraph/decision.py
- taskcluster/taskgraph/morph.py 1 addition, 41 deletionstaskcluster/taskgraph/morph.py
- taskcluster/taskgraph/util/taskcluster.py 15 additions, 0 deletionstaskcluster/taskgraph/util/taskcluster.py
Please register or sign in to comment