Yes, I can create a PR to reintroduce the test and do some changes without
impacting the master branch.
Regards
JB
On 11/29/2017 02:00 PM, Giuseppe Gerla wrote:
Just to be sure... could you try with surefire 2.16.
Because during my investigation I had problems with both 2.18.1 and 2.20.1
Just to be sure... could you try with surefire 2.16.
Because during my investigation I had problems with both 2.18.1 and 2.20.1
(that is better than 2.20.0 but not problem free).
Regards
Giuseppe
2017-11-29 7:54 GMT+01:00 Grzegorz Grzybek :
> Thanks!
>
> I'll have a
Thanks!
I'll have a look too - but not this week. @Ignoring it is good idea for now
- timeouts proved to be working well for long time now.
regards
Grzegorz Grzybek
2017-11-29 7:17 GMT+01:00 Jean-Baptiste Onofré :
> I excluded MavenTest and now the build is way more stable
I excluded MavenTest and now the build is way more stable on Jenkins.
I will investigate.
Regards
JB
On 11/29/2017 06:16 AM, Grzegorz Grzybek wrote:
@Mikael - that's what I observed too - 2.20.1 had this (intermittent) 30
seconds timeout after test finishes.
I don't have time (before Code
@Mikael - that's what I observed too - 2.20.1 had this (intermittent) 30
seconds timeout after test finishes.
I don't have time (before Code Europe conf.) to check what's the problem
now, but I won't just leave it unexplained...
best regards
Grzegorz Grzybek
2017-11-28 23:10 GMT+01:00 Mikael
Hi Mikael,
that's not the same issue here.
We updated to surefire 2.20.1 (2.20.0 didn't work).
Regards
JB
On 11/28/2017 11:10 PM, Mikael Åsberg wrote:
I've had problems with Pax Exam and surefire after version 2.18.1 of surefire.
Version 2.18.1 was working fine, but versions after that would
I've had problems with Pax Exam and surefire after version 2.18.1 of
surefire. Version 2.18.1 was working fine, but versions after that would
often fail with errors along these lines:
[ERROR] org.apache.maven.surefire.booter.SurefireBooterForkException:
ExecutionException The forked VM
I know, but I'm checking if there is no missing config.
Regards
JB
On 11/27/2017 11:40 AM, Grzegorz Grzybek wrote:
MavenTest was my non-KarafTestSupport test case. I wanted to be able to
configure Maven resolver and Jetty server to test timeouts, http proxies,
etc.
regards
Grzegorz Grzybek
MavenTest was my non-KarafTestSupport test case. I wanted to be able to
configure Maven resolver and Jetty server to test timeouts, http proxies,
etc.
regards
Grzegorz Grzybek
2017-11-27 10:52 GMT+01:00 Jean-Baptiste Onofré :
> I found something interesting: MavenTest doesn't
I found something interesting: MavenTest doesn't extend KarafTestSupport. So,
I'm checking the difference between the config in KarafTestSupport (where all
tests pass without problem) and the config in MavenTest.
I'm on it and keep you posted ;)
Regards
JB
On 11/27/2017 09:18 AM,
Yeah, I remember I got issues with surefire.
However, I don't think it's related in that case (different issue).
So, let me exclude this test for now to give us time to investigate.
Regards
JB
On 11/27/2017 08:28 AM, Grzegorz Grzybek wrote:
Hello
I found that maven-surefire-plugin 2.20+ has
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
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
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.
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
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
Hi Giuseppe,
not sure I follow you. You mean you change the itest on your local copy ?
Regards
JB
On 11/25/2017 11:05 PM, Giuseppe Gerla wrote:
Hi JB
If you remember i had the same problem.
After several week and several investigativo, i discovered some difference
beteeen my itest and
Hi JB
If you remember i had the same problem.
After several week and several investigativo, i discovered some difference
beteeen my itest and activemq itest. So i changed my itest sturtup. Now It
seems solved.
Regards
Giuseppe
Il 25 nov 2017 17:44, "Jean-Baptiste Onofré" ha
Hi,
randomly (only for this itest), the container never came up (pax exam).
Regards
JB
On 11/25/2017 09:56 AM, Giuseppe Gerla wrote:
Hi JB
what type of failure?
Regards
Giuseppe
2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré :
Hi guys,
Our Jenkins jobs are not very
Hi JB
what type of failure?
Regards
Giuseppe
2017-11-25 7:20 GMT+01:00 Jean-Baptiste Onofré :
> Hi guys,
>
> Our Jenkins jobs are not very stable (both master and PR) due to the
> MavenTest which randomly fails (but often).
>
> I will remove this test from master and move
Hi guys,
Our Jenkins jobs are not very stable (both master and PR) due to the MavenTest
which randomly fails (but often).
I will remove this test from master and move it to a dedicated PR to investigate
(but at least it won't impact our nightly builds and PRs).
Regards
JB
--
Jean-Baptiste
21 matches
Mail list logo