Closed
Bug 798241
Opened 12 years ago
Closed 12 years ago
Codesighs diffs taking 20-30 minutes to either run or time out on Linux mock slaves
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: philor, Unassigned)
References
Details
(Whiteboard: [codesighs])
It's a confusing confusing situation, but:
* on non-try we don't do codesighs diffs because of bug 798238, and there generating just the number from the current log takes just a few seconds
* on try on OS X, we successfully do codesighs diffs, and take around 4 or 5 minutes for the buildstep
* on try on Linux prior to bug 798225 shutting it off, we successfully did codesighs diffs, and they either took 30 minutes for the buildstep (current and diff), or they took 1200 seconds without output to not even get the current number done before being timed out
It would be a somewhat less confusing situation if not for that last fact - on non-try, with no old log around, maybe 30 seconds, on try, with an old log around which should not be touched or looked at until after that first and only number that's generated on non-try gets generated, frequent 1200 second timeouts before that first number is done.
Reporter | ||
Comment 1•12 years ago
|
||
bug 798798 to stop running it anywhere at all, bug 668219 to delete every bit of the code that ran it
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Assignee | ||
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•