Closed
Bug 842987
Opened 12 years ago
Closed 12 years ago
release runner didn't mark 20.0b1 as failed
Categories
(Release Engineering :: Release Automation, defect, P3)
Release Engineering
Release Automation
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: bhearsum, Unassigned)
References
Details
(Whiteboard: [shipit])
Firefox/Fennec 20.b1 failed during release sanity this morning but didn't reset the ready state or update the status on ship it. I found an attempt to in the log:
2013-02-20 03:35:16,646 - INFO - mark as failed Fennec-20.0b1-build1
2013-02-20 03:35:16,830 - INFO - mark as failed Firefox-20.0b1-build1
But no error message.
|
Reporter | |
Updated•12 years ago
|
Whiteboard: [shipit]
|
|
Reporter | |
Updated•12 years ago
|
Priority: -- → P3
|
|
Reporter | |
Comment 1•12 years ago
|
||
bug 843703 added some better logging for this - we'll get exceptions in the logs for any http errors that we hit. However, we haven't this again so I'm going to close this INCOMPLETE.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INCOMPLETE
|
Assignee | |
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•