Hold Targeter leaves lockfiles after failure
Bug #977358 reported by
Thomas Berezansky
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Low
|
Unassigned |
Bug Description
I have attempted to make the hold targeter less likely to leave a lockfile sitting around after failures in the branch below. It appears to work for us when errors do crop up.
Mainly it consists of a number of try/otherwise blocks wrapped around the existing code sets.
I dunno if this should be dropped into 2.2 or not.
Changed in evergreen: | |
milestone: | none → 2.3.0-alpha2 |
Changed in evergreen: | |
milestone: | 2.3.0-alpha2 → 2.3.0-beta1 |
Changed in evergreen: | |
milestone: | 2.3.0-beta1 → 2.3.0-beta2 |
Changed in evergreen: | |
milestone: | 2.3.0-beta2 → 2.3.0-rc1 |
Changed in evergreen: | |
milestone: | 2.3.0-rc1 → 2.3.0 |
Changed in evergreen: | |
milestone: | 2.3.0 → 2.3.1 |
Changed in evergreen: | |
status: | New → Confirmed |
importance: | Undecided → Low |
Changed in evergreen: | |
milestone: | 2.4.0-alpha1 → 2.4.0-beta |
Changed in evergreen: | |
assignee: | nobody → Jason Stephenson (jstephenson) |
Changed in evergreen: | |
status: | Confirmed → Fix Committed |
assignee: | Jason Stephenson (jstephenson) → nobody |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reassigning to 2.4 as this might be more new featurish now that 2.3.0 has come and gone.