Hi Emmanuel,

From what I've seen checking the logs, this test is failing on ApacheDS:
org.apache.directory.server.replication.ClientServerReplicationIT.testRebootConsumer()

We also have weird out of memory and heap size issues on LDAP API and Studio 
jobs.
I don't understand why these build would suddenly fail on issues like that 
after having run for years now pretty fine with the current settings...

I will have a look at the configuration and tweak a few things here and there.

There are also other failed build due to JVM being terminated, but I'm afraid 
we can't do anything with these ones.
The machine on which the jobs are executed was probably overloaded at some 
point and had to release resources.
These ones look like false-positive to me, because usually they go back up at 
the next build.

Anyways, I'll definitely have look at that today.

Regards,
Pierre-Arnaud

 
On 6 mars 2013, at 08:10, Emmanuel Lécharny <[email protected]> wrote:

> Hi guys,
> 
> we have failing builds every day on Jenkins. We probably have some tests
> that fail due to some time condition (for instance, the
> ClientAbandonRequestTest.testCancelSearch test is failing on slow machines).
> 
> We also have a test failing on eplication (moddn) that need to be fixed
> (Pierre-Arnaud has @Ignored it atm).
> 
> We need to investigate those breakages.
> 
> -- 
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com 
> 

Reply via email to