I can't comment on the ActiveMQ builds, but I can say that Jenkins is really flaky lately. Last time I counted (last week), we had 20% of the Drill and Mahout builds failing due to issues with Jenkins. It is also common if you look into the build queues to see jobs that normally take 20 minutes to be hung for 6-7 days.
I don't know what the problem is. The Jenkins instance that we run in-house seems pretty stable, but it doesn't have the load that Apache's instance has. My own gut feeling is that there is something really flaky about how things are wired in the Apache install. I have also had next to no response in asking questions about this on the builds mailing list. If you send email to infra@ about this, they say use builds@. If you send email builds@, it gets ignored mostly. Very hard to figure this out, very frustrating to not be able to find any hints. On Sat, Mar 30, 2013 at 2:10 AM, seba.wag...@gmail.com < seba.wag...@gmail.com> wrote: > Is it possible that there is something wrong with the ActiveMQ builds? > It just seems to me strange that the builds take 3 to 6 hours. Somehow they > are configured to run daily now. I think they are bound to run only on > ubuntu. Consequently ubuntu nodes on Jenkins are permanently blocked. > > Those are the projects: > https://builds.apache.org/job/ActiveMQ/1256/ > https://builds.apache.org/job/ActiveMQ-Java7/169/ > > Maybe its time for extending the build infrastructure @ ASF with some new > nodes? :) > > Thanks, > Sebastian > -- > Sebastian Wagner > https://twitter.com/#!/dead_lock > http://www.webbase-design.de > http://www.wagner-sebastian.com > seba.wag...@gmail.com >
