Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Travis is timing out fairly often since the addition of 5.32 #136

ndawe opened this Issue Dec 11, 2012 · 3 comments


None yet
3 participants

cdeil commented Dec 11, 2012

Actually for the one you mention git submodule update timed out:
Build 198.2: https://travis-ci.org/rootpy/rootpy/jobs/3606285

I looked through all rootpy and root_numpy failed builds, and found two cases where the tarball download timed out:
Build 147: https://travis-ci.org/rootpy/rootpy/jobs/3583469
Build 152.2: https://travis-ci.org/rootpy/rootpy/jobs/3583469

For the other builds you can see that they typically download the tarballs in seconds, so I guess these cases mean there was a problem on the travis or github side.
It's annoying, but there's nothing we can do and three false alarms is not so bad, it only takes a minute to look at the build log and see that there wasn't really a build error.

@ndawe I'll label this issue long-term, we can just keep an eye on this and if the timeout rate remains low we can close it in a few months.


pwaller commented Dec 11, 2012

One possibility is to put our own timeout code in, and to proceed anyway. Then we get random tests of different installed dependencies ;-)


pwaller commented Feb 18, 2013

@ndawe, @cdeil I'm closing this since looking at the build history it doesn't seem like an issue. Please reopen if it is.

@pwaller pwaller closed this Feb 18, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment