Closed
Bug 957337
Opened 11 years ago
Closed 11 years ago
Mozharness swallows return_code of a talos run if it is 1
Categories
(Release Engineering :: Applications: MozharnessCore, defect)
Release Engineering
Applications: MozharnessCore
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jlund, Assigned: jlund)
Details
Attachments
(1 file)
2.71 KB,
patch
|
mozilla
:
review+
jlund
:
checked-in+
|
Details | Diff | Splinter Review |
This is my fault. I submitted a talos retry patch last month that I thought would support 0 and 1 return codes from talos while getting mozharness to set an ERROR for anything else.
This was my patch: http://hg.mozilla.org/build/mozharness/rev/1913406e2d96
I should have caught that buildbot_status() will set the return code if we don't explicitly set_return_code=False. I wanted it to set the return code but I didn't want it to overwrite it if it was 1! Patch incoming.
Assignee | ||
Comment 1•11 years ago
|
||
Attachment #8356818 -
Flags: review?(aki)
Comment 2•11 years ago
|
||
Comment on attachment 8356818 [details] [diff] [review]
957337_Mozharness_swallows_return_code_talos_if_1-040114.diff
You could also
worst_log_level = ERROR
worst_tbpl_status = TBPL_FAILURE
if self.return_code == 1:
worst_log_level = WARNING
worst_tbpl_status = TBPL_WARNING
and then calling the worst_level() for each. I'm fine with this, though.
Attachment #8356818 -
Flags: review?(aki) → review+
Assignee | ||
Comment 3•11 years ago
|
||
pushed to default with changes as per review: https://hg.mozilla.org/build/mozharness/rev/01bcddcbd6d4
Assignee | ||
Updated•11 years ago
|
Attachment #8356818 -
Flags: checked-in+
Comment 4•11 years ago
|
||
Merged mozharness (not getting CCed to this bug).
Assignee | ||
Comment 5•11 years ago
|
||
whoops, this has been resolved
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Component: General Automation → Mozharness
You need to log in
before you can comment on or make changes to this bug.
Description
•