Closed
Bug 1265074
Opened 9 years ago
Closed 7 years ago
push to releases script hangs instead of halting when self.fatal is called from one of the threads in a pool
Categories
(Release Engineering :: Release Automation: Other, defect, P5)
Release Engineering
Release Automation: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jlund, Unassigned)
References
Details
e.g. https://public-artifacts.taskcluster.net/tAuq_T8iR3qIX2R7CzrhoA/0/public/logs/live_backing.log
when http://hg.mozilla.org/mozilla-central/file/354cb3932e36/testing/mozharness/scripts/release/push-candidate-to-releases.py#l169 is called within http://hg.mozilla.org/mozilla-central/file/354cb3932e36/testing/mozharness/scripts/release/push-candidate-to-releases.py#l190
|
||
Updated•8 years ago
|
Priority: -- → P5
|
||
Comment 1•7 years ago
|
||
We moved this functionality now in 3.6 beetmoverscript [1]. Closing this as it outlived its usefulness.
[1]: https://github.com/mozilla-releng/beetmoverscript/blob/master/beetmoverscript/script.py#L115
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•