[SERVER-58146] Task generator outcomes are not reproducible Created: 29/Jun/21  Updated: 27/Oct/23  Resolved: 27/Oct/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Andrew Morrow (Inactive) Assignee: [DO NOT ASSIGN] Backlog - Decision Automation Group (DAG) (Inactive)
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Decision Automation Group
Operating System: ALL
Participants:

 Description   

Task generation is run inline in every build, and the resulting task splits are based on recent historical task timing data. However, the resulting splits are not persisted and associated with commits or commit ranges. One consequence of this is that if you check out an older commit and submit a patch build above it, the task generators may generate different task splits than the base commit did (or would have). Another consequence is the introduction new failure modes, where task generation itself fails, which generally renders a patch build invalid. It would be better if task splits were deterministic/reproducible at each commit, and ideally precomputed: then they could not fail and no time would needed to be spent in the build to obtain them.


Generated at Thu Feb 08 05:43:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.