Closed Bug 873928 Opened 11 years ago Closed 10 years ago

Intermittent command timed out: 3600 seconds without output, attempting to kill fetching b2g bits from gitmo

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure) 

https://tbpl.mozilla.org/php/getParsedLog.php?id=23143110&tree=Mozilla-Inbound
b2g_mozilla-inbound_emulator_dep on 2013-05-19 19:24:09 PDT for push 86f54487e3e4
slave: bld-linux64-ix-025

19:30:59     INFO - Fetching projects:  97% (82/84)  remote: Counting objects: 1, done.[K
19:30:59     INFO -  remote: Total 1 (delta 0), reused 0 (delta 0)[K
19:30:59     INFO -  Unpacking objects: 100% (1/1)   
19:30:59     INFO - Unpacking objects: 100% (1/1), done.
19:31:00     INFO -  From https://git.mozilla.org/external/caf/platform/system/vold
19:31:00     INFO -   * [new tag]         AU_LINUX_ANDROID_JB_2.5.6.04.02.02.093.037 -> AU_LINUX_ANDROID_JB_2.5.6.04.02.02.093.037

command timed out: 3600 seconds without output, attempting to kill
process killed by signal 9
program finished with exit code -1

So close, already to the 82nd one!
Product: mozilla.org → Release Engineering
Depends on: 961042
Hi Hal, do you have any idea why we are getting these timeouts cloning from git? Who is the correct person to ask? :-)
Flags: needinfo?(hwine)
Ed -- no idea at the moment. Certainly nothing obvious. It does seem to be increasing, but (at first glance) there isn't sufficient information in the logs to point a finger. I think we'll need to get some better debug output to catch this.
Flags: needinfo?(hwine)
See Also: → 990344
MARKER: git.mozilla.org updated to v1.9.2 at 1000 PT this morning
Since the update of the git server on April 24, there has been no occurrence of a timeout associated with git.m.o. \o/ That fixed it!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Split comment 127 and comment 128 into bug 1027668, since this happened again today.
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.