dmwm / continuousintegration Goto Github PK

The different scripts need a way to handle flakiness like

• github's issue API goes down
• github's git stuff doesn't respond
• ZMQ segfaults

It could/should be handled in try_daemon.py to either retry the build or pass back a "null result" identifier.

Initially a place for Jenkins to post about comparisons of python 2.7 with python 2.6. Later switched to be the place for 2016 tests after the transition to python 2.7 was made

Currently, it takes longer to get the job status out of jenkins than it takes to actually run the jobs themselves. This is because I use a big depth=2 query against the API, and that takes processing a LOT of of logfiles for jenkins to compile. I need to turn that into several depth=0 queries against the specific parts we're looking to pull out

Need to make the try_patch bot ignore/retry those.

hudson.plugins.git.GitException: Command "git fetch -t git://github.com/dmwm/WMCore.git +refs/heads/:refs/remotes/origin/" returned status code 128:
stdout:
stderr: github.com[0: 207.97.227.239]: errno=Connection timed out
fatal: unable to connect a socket (Connection timed out)

at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:838)
at hudson.plugins.git.GitAPI.launchCommand(GitAPI.java:800)
at hudson.plugins.git.GitAPI.fetch(GitAPI.java:197)
at hudson.plugins.git.GitAPI.fetch(GitAPI.java:1046)
at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1142)
at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1064)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2308)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)

ERROR: Could not fetch from any repository
FATAL: Could not fetch from any repository
hudson.plugins.git.GitException: Could not fetch from any repository
at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1154)
at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1064)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2308)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)

This issue will contain a twice-daily update of which tests are changing in the DMWM baseline. Hopefully we will spot unstable tests this way as well as any problems that get inadvertently checked in.

New year, new issue.