Re: [UPDATE] MavenTest itest fails randomly but often

2017-11-26 Thread Grzegorz Grzybek
Hmm, I didn't check 2.20.1, rather 2.20. But if anything goes wrong, I think there still may be some surefire issue. regards Grzegorz 2017-11-27 8:37 GMT+01:00 Achim Nierbeck : > Hi Grzegorz, > > interesting that you have issues with that version. > I just updated pax-web to use 2.20.1 and all t

Re: [UPDATE] MavenTest itest fails randomly but often

2017-11-26 Thread Achim Nierbeck
Hi Grzegorz, interesting that you have issues with that version. I just updated pax-web to use 2.20.1 and all tests are passing (finally) regards, Achim 2017-11-27 8:28 GMT+01:00 Grzegorz Grzybek : > Hello > > I found that maven-surefire-plugin 2.20+ has some problems with pax-exam. > I'd love

Re: [UPDATE] MavenTest itest fails randomly but often

2017-11-26 Thread Grzegorz Grzybek
Hello I found that maven-surefire-plugin 2.20+ has some problems with pax-exam. I'd love to investigate the exact cause, but didn't have time yet... The surefire/failsafe issue is https://issues.apache.org/jira/browse/SUREFIRE-1374 And in my (jboss fuse) integration tests I stayed with 2.19.x. r

Gitbox down

2017-11-26 Thread Jean-Baptiste Onofré
Hi, it seems GitBox is down (timing out). I don't see anything on status.apache.org, I will ping INFRA. Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com

Re: [UPDATE] MavenTest itest fails randomly but often

2017-11-26 Thread Jean-Baptiste Onofré
Hmm, not sure it's related as we use the same KarafTestSupport in bunch of other itest. I will exclude the MavenTest for now, and investigate. Thanks anyway ! Regards JB On 11/26/2017 09:50 AM, Giuseppe Gerla wrote: Hi JB although the tests worked on my PC, very often they went wrong on the

Re: [UPDATE] MavenTest itest fails randomly but often

2017-11-26 Thread Giuseppe Gerla
Hi JB although the tests worked on my PC, very often they went wrong on the jenkins machine. I did several experiments to find the problem, but it was very difficult to understand it. What I understood is that for some reason the container is too slow to come up and the timeout of pax expired befor