Closed
Bug 1268310
Opened 9 years ago
Closed 9 years ago
Thunderbird 45.1b1 isn't starting
Categories
(Release Engineering :: Release Automation: Other, defect)
Release Engineering
Release Automation: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: nthomas)
References
Details
Attachments
(1 file)
855 bytes,
patch
|
jlund
:
review+
kmoir
:
checked-in+
|
Details | Diff | Splinter Review |
... because it doesn't match the expectation r"Thunderbird-\d+\.0b\d+-build\d+" at http://hg.mozilla.org/build/tools/file/old-release-runner/buildfarm/release/release-runner.py#l49 and we get this in bm81's log:
2016-04-27 18:15:44,529 - DEBUG - "GET /releases/Thunderbird-45.1b1-build1 HTTP/1.1" 200 1964
2016-04-27 18:15:44,530 - INFO - No releases to handle in [{'comment....
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8746326 -
Flags: review?(jlund)
Updated•9 years ago
|
Attachment #8746326 -
Flags: review?(jlund) → review+
Comment 2•9 years ago
|
||
Will the 45.1b1 designation break anything else in the build and distribution process?
Might it be better to kill 45.1b1, and rerun as 45.0b5?
Comment 3•9 years ago
|
||
in any event, please don't land until I've sorted out some other pending questions. thanks.
Assignee | ||
Comment 4•9 years ago
|
||
It's possible, since you're munging together the esr and beta naming styles, but I doubt we can know for sure until we try.
Comment 5•9 years ago
|
||
Please land and we'll go for it.
We will do the build named 45.1b1
Flags: needinfo?(nthomas)
Updated•9 years ago
|
Attachment #8746326 -
Flags: checked-in+
Comment 6•9 years ago
|
||
updated release runner on bm81, you should be able to start your build again
Comment 7•9 years ago
|
||
and restarted release runner too
Assignee | ||
Comment 8•9 years ago
|
||
Release is running now, thanks Kim.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(nthomas)
Resolution: --- → FIXED
Assignee | ||
Comment 9•9 years ago
|
||
The landing was http://hg.mozilla.org/build/tools/rev/9e7b2f717a07
You need to log in
before you can comment on or make changes to this bug.
Description
•