Rob Duff commented on Bug JENKINS-24179

Thanks very much for the very speed reply, Mark! I'll take this up with the msysgit folks.

For the sake of completeness (for those who may wander to this issue), I've found something suspicious. We have two different builds running at the same time on the same machine in two different executors, and they're cloning the same repository. Here is the output of the first, which passed:

11:51:45 Cloning repository ssh://g...@git.dev.faked:7999/re/core-binaries.git
11:51:46 Fetching upstream changes from ssh://g...@git.dev.faked:7999/re/core-binaries.git
11:51:46 Fetching upstream changes from ssh://g...@git.dev.faked:7999/re/core-binaries.git
11:51:47 Checking out Revision 5e4da3e3994dbe8b7aa0b995566c479dce51f474 (core-binaries/master

Here is the output of the second, which failed:

11:51:45 Cloning repository ssh://g...@git.dev.faked:7999/re/core-binaries.git
11:51:46 Fetching upstream changes from ssh://g...@git.dev.faked:7999/re/core-binaries.git
11:51:46 Fetching upstream changes from ssh://g...@git.dev.faked:7999/re/core-binaries.git
12:01:46 ERROR: Timeout after 10 minutes
12:01:46 FATAL: Failed to fetch from ssh://g...@git.dev.faked:7999/re/core-binaries.git

We have lots of repositories, but I bet it only happens when the same repository is cloned at the same time. The timing makes me suspicious that this might be the issue.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to