Re: DocumentRDB builds time out on Jenkins

On 10.12.15 8:08 , Julian Reschke wrote: On 2015-12-10 15:58, Julian Reschke wrote: On 2015-12-10 15:22, Marcel Reutegger wrote: Hi, hmm, this could be similar to https://issues.apache.org/jira/browse/OAK-2704 I had a closer look at the DOCUMENT_RDB fixture and I think the problem is with

Re: DocumentRDB builds time out on Jenkins

On 2015-12-11 16:07, Michael Dürig wrote: ... And build 611 () is going to timeout again (this time for the RDBMK JDK 1.7 integration tests). No it didn't:

Re: DocumentRDB builds time out on Jenkins

On 11.12.15 4:19 , Julian Reschke wrote: On 2015-12-11 16:07, Michael Dürig wrote: ... And build 611 () is going to timeout again (this time for the RDBMK JDK 1.7 integration tests). No it didn't:

Re: DocumentRDB builds time out on Jenkins

Hi, On 10/12/15 15:58, "Julian Reschke" wrote: >Anyway, that still doesn't explain the confusion in the surefire logs, no? I think I found a cause of this one. The custom Parallelized runner we use has a bug - if a test class runs for longer than 10 minutes, it will

Re: DocumentRDB builds time out on Jenkins

On 2015-12-10 15:58, Julian Reschke wrote: On 2015-12-10 15:22, Marcel Reutegger wrote: Hi, hmm, this could be similar to https://issues.apache.org/jira/browse/OAK-2704 I had a closer look at the DOCUMENT_RDB fixture and I think the problem is with the createNodeStore() method. The method is

Re: DocumentRDB builds time out on Jenkins

On 10.12.15 11:54 , Michael Dürig wrote: On 10.12.15 11:40 , Tomek Rekawek wrote: Bertrand already pointed out the appropriate option. Passing **/target/unit-tests.log as the “Files to archive” should do the trick. Ok, I added a post build action for archiving **/target/unit-tests.log.

Re: DocumentRDB builds time out on Jenkins

On Thu, Dec 10, 2015 at 11:27 AM, Michael Dürig wrote: > On 10.12.15 11:02 , Tomek Rekawek wrote: >> ...Maybe we can change the configuration, so the >> target/unittest.log file will be archived if the job is failed?... > > This would be useful anyway but I think so far no one

Re: DocumentRDB builds time out on Jenkins

On 10.12.15 11:02 , Tomek Rekawek wrote: I’ve noticed that the failed builds can be assigned to a few machines. For instance, builds on ubuntu-6, ubuntu-5, H11 and H10 fails almost every time. On the other hand, all builds on the jenkins-ubuntu-1404-4gb succeedes. Good find! Are these

Re: DocumentRDB builds time out on Jenkins

On 2015-12-10 14:57, Tomek Rekawek wrote: Hi, I spent some time analysing the logs and I found out a strange thing. On a “slow” machine, in the surefire logs for the AtomicCounterTest (which takes 63 sec while it should 3 sec), following test case appears [1]: It’s a test case from a

Re: DocumentRDB builds time out on Jenkins

Hi, I spent some time analysing the logs and I found out a strange thing. On a “slow” machine, in the surefire logs for the AtomicCounterTest (which takes 63 sec while it should 3 sec), following test case appears [1]: It’s a test case from a completely different class. I downloded all

Re: DocumentRDB builds time out on Jenkins

Hi, hmm, this could be similar to https://issues.apache.org/jira/browse/OAK-2704 I had a closer look at the DOCUMENT_RDB fixture and I think the problem is with the createNodeStore() method. The method is supposed to create independent node store instances, but the RDB implementation uses an

Re: DocumentRDB builds time out on Jenkins

On 2015-12-10 15:22, Marcel Reutegger wrote: Hi, hmm, this could be similar to https://issues.apache.org/jira/browse/OAK-2704 I had a closer look at the DOCUMENT_RDB fixture and I think the problem is with the createNodeStore() method. The method is supposed to create independent node store

Re: DocumentRDB builds time out on Jenkins

On 9.12.15 11:58 , Julian Reschke wrote: On 2015-12-09 09:42, Michael Dürig wrote: Hi, In the last 5 build on our Jenkins instance [1] we always had one of the DocumentRDB jobs timing out [2]. This means the job didn't complete within 90 minutes. This is not because we are close to the

Re: DocumentRDB builds time out on Jenkins

On 2015-12-09 09:42, Michael Dürig wrote: Hi, In the last 5 build on our Jenkins instance [1] we always had one of the DocumentRDB jobs timing out [2]. This means the job didn't complete within 90 minutes. This is not because we are close to the limit as regular builds take roughly 30 minutes.

Re: DocumentRDB builds time out on Jenkins

On 9.12.15 12:41 , Julian Reschke wrote: Something must be way wrong as the build either takes ~30 minutes or it times out after 90 minutes. There is quite a difference here. Maybe we need to go through the log files and compare test execution times of individual tests between timed out and

Re: DocumentRDB builds time out on Jenkins

On 2015-12-09 12:02, Michael Dürig wrote: On 9.12.15 11:58 , Julian Reschke wrote: On 2015-12-09 09:42, Michael Dürig wrote: Hi, In the last 5 build on our Jenkins instance [1] we always had one of the DocumentRDB jobs timing out [2]. This means the job didn't complete within 90 minutes.

Re: DocumentRDB builds time out on Jenkins

On 9.12.15 12:02 , Michael Dürig wrote: Do you have any suggestions? Something must be way wrong as the build either takes ~30 minutes or it times out after 90 minutes. There is quite a difference here. Maybe we need to go through the log files and compare test execution times of