Originally posted as a comment in bug 1165335. I was seeing the endless "generating bug suggestions" loop on this Windows XP debug m(oth) job, which isn't TC-based: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/fx-team-win32-debug/1441721374/fx-team_xp-ix-debug_test-mochitest-other-bm112-tests1-windows-build522.txt.gz https://treeherder.mozilla.org/#/jobs?repo=fx-team&revision=20cc75c647f1&filter-searchStr=xp%20m%28oth Camd looked into it. His reply below: > The log parsing had failed for some reason (I don't know why). I went into the DB directly, and set the status in the job_log_url table to "pending" from "failed" Then went into TH and it showed as pending. And a second later, it finished. > Would you open a new bug? I think perhaps how we should handle this is that, if the user clicks on a job with a failed parse status, that we should retry it anyway. It's low overhead and may just kick things into working. Maybe we should also figure out WHY it fails sometimes. But that could be a timeout or something. The bug might also mention we should retry parsing if it fails (if we don't already).
I don't think this added complexity is worth it.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.