If true a sleep would workaround it. That said i dont reproduce it on
ubuntu, even on very fast machines so not sure. Maybe local setup related?
Le dim. 17 juin 2018 21:49, Mark Struberg a
écrit :
> Just looked what we do in fb_tomee8. And found the following:
>
> @Ignore //X TODO see TOMEE-2139
Just looked what we do in fb_tomee8. And found the following:
@Ignore //X TODO see TOMEE-2139 currently broken due to #f24c42e2212c575
We cannot release with this test.
LieGrue,
strub
> Am 17.06.2018 um 14:03 schrieb Romain Manni-Bucau :
>
> Can need a clean to pass IIRC. Code is unrelated to
Can need a clean to pass IIRC. Code is unrelated to tomcat actually
Le dim. 17 juin 2018 12:16, Mark Struberg a
écrit :
> That rotating test seems to stick.
>
> Might have to do with a minor tomcat behaviour change.
> Something which is at least not behaving stochastic and we can work on it.
> W
That rotating test seems to stick.
Might have to do with a minor tomcat behaviour change.
Something which is at least not behaving stochastic and we can work on it.
Will try to tackle it tonight.
LieGrue,
strub
> Am 17.06.2018 um 11:50 schrieb Mark Struberg :
>
> That's the goal :D
>
> I will
I also won't be around until the evening, but happy to check it out and
kick off the release if we're looking good.
Jon
On Sun, 17 Jun 2018, 10:51 Mark Struberg, wrote:
> That's the goal :D
>
> I will be offline this afternoon, just like to providing feedback and pick
> up in the evening again.
That's the goal :D
I will be offline this afternoon, just like to providing feedback and pick up
in the evening again.
Those are all stochastic failures. Once you resume from there they will likely
work fine again :(
Of course that's frustrating to a potential new committer, so we should rather
A computer issue due to the need of a time related test?
The lastest can be a network issue on mac (already saw) or defaulting of
our net interface selection.
Le dim. 17 juin 2018 11:37, Mark Struberg a
écrit :
> And another one which seems regularly failing since 2 years:
>
> [ERROR] Tests run:
I'll take a look - I think my last build was green. If we sort these out,
are we good to release? I'm happy to do the actual release.
Jon
On Sun, 17 Jun 2018, 10:37 Mark Struberg, wrote:
> And another one which seems regularly failing since 2 years:
>
> [ERROR] Tests run: 1, Failures: 1, Errors
And another one which seems regularly failing since 2 years:
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 38.736
s <<< FAILURE! - in org.apache.openejb.itest.legacy.LegacyServerTest
[ERROR] test(org.apache.openejb.itest.legacy.LegacyServerTest) Time elapsed:
38.661 s
OpenJPA updated to 2.4.3.
But still getting random test errors.
Failed tests:
ManagedScheduledExecutorServiceTest.triggerRunnableSchedule:124 null
triggerRunnableSchedule(org.apache.openejb.threads.ManagedScheduledExecutorServiceTest)
Time elapsed: 0.836 sec <<< FAILURE!
java.lang.Assertio
10 matches
Mail list logo
