You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openmeetings.apache.org by "seba.wagner@gmail.com" <se...@gmail.com> on 2013/03/30 02:10:56 UTC
ActiveMQ build takes 3 to 6 hours on Jenkins
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.wagner@gmail.com
Re: ActiveMQ build takes 3 to 6 hours on Jenkins
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
I had the same impression, build servers seem to be a grey area. I guess so
far they run pretty "self managed".
However the number of projects grow constantly and continuous builds are a
central part in every project.
Those concrete builds seem to run 3 and 6 hours really, not because they
are queud, its the job itself. Errors in Jenkins so far had the effect that
the build just immediately stopped as failed.
But its not clear if that is an accident or a desired behaviour for those
concrete builds. The only ones that can really answer that are the devs @
activemq.
Sebastian
2013/3/30 Ted Dunning <te...@gmail.com>
> 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.wagner@gmail.com <
> seba.wagner@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.wagner@gmail.com
> >
>
--
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com
Re: ActiveMQ build takes 3 to 6 hours on Jenkins
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
I had the same impression, build servers seem to be a grey area. I guess so
far they run pretty "self managed".
However the number of projects grow constantly and continuous builds are a
central part in every project.
Those concrete builds seem to run 3 and 6 hours really, not because they
are queud, its the job itself. Errors in Jenkins so far had the effect that
the build just immediately stopped as failed.
But its not clear if that is an accident or a desired behaviour for those
concrete builds. The only ones that can really answer that are the devs @
activemq.
Sebastian
2013/3/30 Ted Dunning <te...@gmail.com>
> 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.wagner@gmail.com <
> seba.wagner@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.wagner@gmail.com
> >
>
--
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com
Re: ActiveMQ build takes 3 to 6 hours on Jenkins
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
I had the same impression, build servers seem to be a grey area. I guess so
far they run pretty "self managed".
However the number of projects grow constantly and continuous builds are a
central part in every project.
Those concrete builds seem to run 3 and 6 hours really, not because they
are queud, its the job itself. Errors in Jenkins so far had the effect that
the build just immediately stopped as failed.
But its not clear if that is an accident or a desired behaviour for those
concrete builds. The only ones that can really answer that are the devs @
activemq.
Sebastian
2013/3/30 Ted Dunning <te...@gmail.com>
> 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.wagner@gmail.com <
> seba.wagner@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.wagner@gmail.com
> >
>
--
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com
Re: ActiveMQ build takes 3 to 6 hours on Jenkins
Posted by Ted Dunning <te...@gmail.com>.
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.wagner@gmail.com <
seba.wagner@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.wagner@gmail.com
>
Re: ActiveMQ build takes 3 to 6 hours on Jenkins
Posted by Ted Dunning <te...@gmail.com>.
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.wagner@gmail.com <
seba.wagner@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.wagner@gmail.com
>
Re: ActiveMQ build takes 3 to 6 hours on Jenkins
Posted by Ted Dunning <te...@gmail.com>.
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.wagner@gmail.com <
seba.wagner@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.wagner@gmail.com
>