Look at the source for the failing tests. What you will likely see
is a lot of threads being started, a delay waiting for them to
complete / hit conditions and then some assertions. If the threads
run into scheduling delays, they may not complete / hit conditions
in time. The timings are gen
> On Nov 19, 2018, at 5:27 PM, Gary Gregory wrote:
>
> HI all:
>
> When I run 'mvn clean verify' on git master, I get test failures on my
> rather busy CPU (~60-90%):
>
> [INFO] Running org.apache.commons.pool2.impl.TestGenericKeyedObjectPool
> [ERROR] Tests run: 63, Failures: 2, Errors: 0,
On Mon, 19 Nov 2018 at 14:27, Gary Gregory wrote:
>
> HI all:
>
> When I run 'mvn clean verify' on git master, I get test failures on my
> rather busy CPU (~60-90%):
>
I can not replicate
∴java -version
openjdk version "11.0.1" 2018-10-16
OpenJDK Runtime Environment 18.9 (build 11.0.1+13)
OpenJDK
HI all:
When I run 'mvn clean verify' on git master, I get test failures on my
rather busy CPU (~60-90%):
[INFO] Running org.apache.commons.pool2.impl.TestGenericKeyedObjectPool
[ERROR] Tests run: 63, Failures: 2, Errors: 0, Skipped: 0, Time elapsed:
177.53 s <<< FAILURE! - in
org.apache.commons.
sebb wrote:
> On 17/03/2010, Mark Thomas wrote:
>> On 17/03/2010 22:04, sebb wrote:
>>
>>> On 17/03/2010, Mark Thomas wrote:
>>>
One of the POOL test cases is failing -
TestSoftRefOutOfMemory.testOutOfMemoryError()
I can't see any recent code changes that may have caused this
On 17/03/2010, Mark Thomas wrote:
> On 17/03/2010 22:04, sebb wrote:
>
> > On 17/03/2010, Mark Thomas wrote:
> >
> > > One of the POOL test cases is failing -
> > > TestSoftRefOutOfMemory.testOutOfMemoryError()
> > >
> > > I can't see any recent code changes that may have caused this and I
> thi
On 17/03/2010 22:04, sebb wrote:
On 17/03/2010, Mark Thomas wrote:
One of the POOL test cases is failing -
TestSoftRefOutOfMemory.testOutOfMemoryError()
I can't see any recent code changes that may have caused this and I think
the recent removal of the testAll code is what has exposed this.
On 17/03/2010, Mark Thomas wrote:
> One of the POOL test cases is failing -
> TestSoftRefOutOfMemory.testOutOfMemoryError()
>
> I can't see any recent code changes that may have caused this and I think
> the recent removal of the testAll code is what has exposed this. On the
> basis that always c
One of the POOL test cases is failing -
TestSoftRefOutOfMemory.testOutOfMemoryError()
I can't see any recent code changes that may have caused this and I
think the recent removal of the testAll code is what has exposed this.
On the basis that always catching Throwable is bad, but there are man
