Closed Bug 1068534 Opened 7 years ago Closed 7 years ago
Failing job has an empty failure summary and cannot be viewed in the log viewer
For the orange job here: http://treeherder-dev.allizom.org/ui/#/jobs?repo=mozilla-central&revision=8252eae8278c&searchQuery=Windows%20XP%2032-bit%20mozilla-central%20opt%20test%20mochitest-browser-chrome-1 The failure summary says: "Failure summary is empty" The log viewer is completely broken (mainly white page): http://treeherder-dev.allizom.org/ui/logviewer.html#?job_id=393349&repo=mozilla-central However the raw log is fine: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-win32/1410912479/mozilla-central_xp-ix_test-mochitest-browser-chrome-1-bm111-tests1-windows-build186.txt.gz And TBPL displays the brief log and a non-empty error summary.
This a consequence of bug 1063923, 1066997 and 1069908. The log parser failed on that job, possibly because of network hiccups. I triggered the log parser again on that job (from the python shell) and it succeeded. I guess we should close this bug and change the priority of the bugs I listed. :edmorley :jeads what do you think about it?
(In reply to Mauro Doglio [:mdoglio] from comment #1) > This a consequence of bug 1063923, 1066997 and 1069908. > The log parser failed on that job, possibly because of network hiccups. > I triggered the log parser again on that job (from the python shell) and it > succeeded. I guess we should close this bug and change the priority of the > bugs I listed. :edmorley :jeads what do you think about it? Agreed; let's dupe this to bug 1069908, since whilst all three of those bugs played a part, that's the bug that would actually mean we can see the parsed log, whereas the others are more UX. I'll adjust the priority of the others accordingly. Thanks :-)
Assignee: mdoglio → nobody
No longer blocks: treeherder-sheriff-transition
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
No longer depends on: 1069908
Resolution: --- → DUPLICATE
Duplicate of bug: 1069908
You need to log in before you can comment on or make changes to this bug.