Closed Bug 817513 Opened 12 years ago Closed 12 years ago

Intermittent clone build tools failed with "command timed out: 1320 seconds without output, attempting to kill"

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: emorley)

References

Details

(Keywords: intermittent-failure, Whiteboard: [buildduty])

Attachments

(1 file)

Saw this a couple of times last week too. Rev4 MacOSX Lion 10.7 mozilla-inbound opt test crashtest on 2012-12-03 00:34:50 PST for push 9049d8cb3de4 slave: talos-r4-lion-050 https://tbpl.mozilla.org/php/getParsedLog.php?id=17550974&tree=Mozilla-Inbound { ========= Started clone build tools failed (results: 2, elapsed: 22 mins, 0 secs) (at 2012-12-03 00:34:52.429837) ========= hg clone http://hg.mozilla.org/build/tools tools in dir /Users/cltbld/talos-slave/test/. (timeout 1320 secs) watching logfiles {} argv: ['hg', 'clone', 'http://hg.mozilla.org/build/tools', 'tools'] environment: Apple_PubSub_Socket_Render=/tmp/launch-F2H8YB/Render CVS_RSH=ssh DISPLAY=/tmp/launch-U7EMPc/org.x:0 HOME=/Users/cltbld LOGNAME=cltbld PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin PWD=/Users/cltbld/talos-slave/test PYTHONPATH=/Library/Python/2.5/site-packages SHELL=/bin/bash SSH_AUTH_SOCK=/tmp/launch-8qiTio/Listeners TMPDIR=/var/folders/qd/srwd5f710sj0fcl9z464lkj00000gn/T/ USER=cltbld VERSIONER_PYTHON_PREFER_32_BIT=no VERSIONER_PYTHON_VERSION=2.7 __CF_USER_TEXT_ENCODING=0x1F5:0:0 using PTY: False command timed out: 1320 seconds without output, attempting to kill process killed by signal 9 program finished with exit code -1 elapsedTime=1320.005669 ========= Finished clone build tools failed (results: 2, elapsed: 22 mins, 0 secs) (at 2012-12-03 00:56:52.458696) ========= }
Should we morph the title to something "Set RETRY status when hg co tools fails" since the error is intermittent?
(In reply to Rail Aliiev [:rail] from comment #1) > Should we morph the title to something "Set RETRY status when hg co tools > fails" since the error is intermittent? Sounds good to me :-) (We could also do bug 758216 at the same time)
(In reply to Rail Aliiev [:rail] from comment #1) > Should we morph the title to something "Set RETRY status when hg co tools > fails" since the error is intermittent? (In reply to Ed Morley [UTC+0; email:edmorley@moco] from comment #2) > (In reply to Rail Aliiev [:rail] from comment #1) > > Should we morph the title to something "Set RETRY status when hg co tools > > fails" since the error is intermittent? > > Sounds good to me :-) (We could also do bug 758216 at the same time) I don't suppose someone could take a look at this? :-)
Attached patch Patch v1Splinter Review
Sets RETRY for the clone build tools step if the return value != 0 Adds a comment to clarify why we have to keep the |retry=False| (which is due to that using retry.py, which is in the very repo we are about to check out, so obviously isn't available to us at this point).
Assignee: nobody → edmorley.bz
Status: NEW → ASSIGNED
Attachment #693289 - Flags: review?(rail)
Comment on attachment 693289 [details] [diff] [review] Patch v1 lgtm
Attachment #693289 - Flags: review?(rail) → review+
Attachment #693289 - Flags: checked-in+
In production.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Blocks: 838325
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: