Yes, I've had wildfly integration tests running there. ----- Original Message ----- > Hi *, > > my attempt to run end to end tests by Travis seems to be exceeding the > resources allowed by Travis. > > I think so because my build [1] ends with "exited with 137" which [2] > describes as exhausted CPUs and/or allocation of more than 3GB memory. > > I am not sure myself, which of the two is my case. Before I spend any > time on that, has anybody ever succeeded to start wildfly inside Travis > and run some integration test? > > Thanks, > > Peter > > [1] https://travis-ci.org/hawkular/hawkular/builds/64250753 > [2] > http://docs.travis-ci.com/user/common-build-problems/#My-build-script-is-... > _______________________________________________ > hawkular-dev mailing list > hawkular-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev

From: "Gary Brown" <gbrown(a)redhat.com&gt; To: "Peter Palaga" <ppalaga(a)redhat.com&gt; Cc: "Discussions around Hawkular development" <hawkular-dev(a)lists.jboss.org&gt; Sent: Wednesday, May 27, 2015 10:51:16 AM Subject: Re: [Hawkular-dev] Hitting Travis Limits https://github.com/hawkular/hawkular-btm Its only running a small amount of tests currently. Regards Gary ----- Original Message ----- > Thanks for the feedback, Gary. Where is your project so that I can > compare it with mine? -- P > > On 2015-05-27 16:31, Gary Brown wrote: > > Yes, I've had wildfly integration tests running there. > > > > ----- Original Message ----- > >> Hi *, > >> > >> my attempt to run end to end tests by Travis seems to be exceeding the > >> resources allowed by Travis. > >> > >> I think so because my build [1] ends with "exited with 137" which [2] > >> describes as exhausted CPUs and/or allocation of more than 3GB memory. > >> > >> I am not sure myself, which of the two is my case. Before I spend any > >> time on that, has anybody ever succeeded to start wildfly inside Travis > >> and run some integration test? > >> > >> Thanks, > >> > >> Peter > >> > >> [1] https://travis-ci.org/hawkular/hawkular/builds/64250753 > >> [2] > >> http://docs.travis-ci.com/user/common-build-problems/#My-build-script-is-... > >> _______________________________________________ > >> hawkular-dev mailing list > >> hawkular-dev(a)lists.jboss.org > >> https://lists.jboss.org/mailman/listinfo/hawkular-dev > >> > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev

> I am not sure myself, which of the two is my case. Before I spend any > time on that, has anybody ever succeeded to start wildfly inside Travis > and run some integration test? We had Hawkular-metrics running on Travis including tests (iirc both with memory and Cassandra backend).

In my case, switching to Travis container-based infrastructure [1][2] helped - see [3] for how to do that. Hard to say which particular aspect of the container-based Travis worker has helped - here are some possible candidates: * more RAM * more CPUs (2 vs. 1.5) * faster network -> faster artifact downloads and therefore shorter total build times -> less probable job timeouts Another important pro for switching to docker workers is that the job starts much faster than with the traditional VM worker. -- P [1] http://docs.travis-ci.com/user/workers/container-based-infrastructure/ [2] http://blog.travis-ci.com/2014-12-17-faster-builds-with-container-based-i... [3] https://github.com/ppalaga/hawkular/commit/351e046c3d383023e5a35fe5c15891... On 2015-05-27 18:06, Thomas Segismont wrote: > Le 27/05/2015 17:02, Heiko W.Rupp a écrit : >>> I am not sure myself, which of the two is my case. Before I spend any >>> time on that, has anybody ever succeeded to start wildfly inside Travis >>> and run some integration test? >> >> We had Hawkular-metrics running on Travis including tests (iirc both >> with memory and Cassandra backend). > > Well, the memory backend is long gone. But as a matter of fact, the > Metrics build starts a Wildfly server twice: first in the rest-tests > module, then in the ptrans module. > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev