Closed Bug 813039 Opened 8 years ago Closed 8 years ago
TBPL should recognise mock's "command timed out: NNNN seconds without output
TBPL currently only recognises "buildbot.slave.commands.TimeoutError". This is fine for buildbot timeouts, due to: https://hg.mozilla.org/build/buildbotcustom/file/tip/steps/unittest.py#l373 However, for mock timeouts we only get "command timed out: NNNN seconds without output". As such, TBPL should match against "command timed out: NNNN seconds without output" instead, which should cover both cases. We can then just cleanup https://hg.mozilla.org/build/buildbotcustom/file/tip/steps/unittest.py#l373 in bug 793782.
Comment on attachment 683067 [details] [diff] [review] Patch v1 Well, let's hope we done have normal and expected "command timed out"s.
Attachment #683067 - Flags: review?(philringnalda) → review+
I couldn't see anything else when testing locally; but suspect the only way we're going to find out is by landing it :-) https://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/rev/8407ba67e1fa
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.