On 18.01.2013 04:23, Apache Jenkins Server wrote:
See<https://builds.apache.org/job/Derby-10.9-suites.All/55/>
< snip>
emit-junit-classpath-jars:
[echo] Running with
jars:<https://builds.apache.org/job/Derby-10.9-suites.All/ws/10.9-head/jars/sane>
[echo] CLASSPATH (environment variable): ${env.CLASSPATH}
emit-junit-classpath:
junit-core:
[junit] Running org.apache.derbyTesting.junit.EnvTest
[junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 0.386 sec
[junit] Running org.apache.derbyTesting.functionTests.tests.derbynet._Suite
[junit] Tests run: 307, Failures: 0, Errors: 0, Time elapsed: 948.924 sec
[junit] Running org.apache.derbyTesting.functionTests.tests.tools._Suite
[junit] Tests run: 115, Failures: 0, Errors: 0, Time elapsed: 217.787 sec
[junit] Running org.apache.derbyTesting.functionTests.tests.demo._Suite
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 21.732 sec
[junit] Running org.apache.derbyTesting.functionTests.tests.lang._Suite
[junit] Tests run: 3438, Failures: 0, Errors: 0, Time elapsed: 7,250.841
sec
[junit] Running org.apache.derbyTesting.functionTests.tests.jdbcapi._Suite
[junit] Tests run: 6601, Failures: 0, Errors: 0, Time elapsed: 2,700.354
sec
[junit] Running org.apache.derbyTesting.functionTests.tests.store._Suite
[junit] Tests run: 293, Failures: 0, Errors: 0, Time elapsed: 4,244.747 sec
[junit] Tests run: 293, Failures: 0, Errors: 0, Time elapsed: 4,244.747 sec
[junit] Running org.apache.derbyTesting.functionTests.tests.engine._Suite
[junit] Tests run: 28, Failures: 0, Errors: 0, Time elapsed: 59.099 sec
[junit] Running org.apache.derbyTesting.unitTests.junit._Suite
[junit] Tests run: 163, Failures: 0, Errors: 0, Time elapsed: 1.812 sec
[junit] Running
org.apache.derbyTesting.functionTests.tests.upgradeTests._Suite
[junit] Tests run: 4041, Failures: 0, Errors: 0, Time elapsed: 5,692.984
sec
[junit] Running
org.apache.derbyTesting.functionTests.suites.EncryptionSuite
[junit] Tests run: 203, Failures: 0, Errors: 0, Time elapsed: 174.668 sec
Seems like this is more than a glitch, the test runs have been failing
multiple times now. The reason seems to be that [some of] the tests take
a lot longer to run, and the run times out after 400 minutes.
Given that observing the running VM is somewhat awkward in the Jenkins
environment (at the ASF), I've tried to increase the amount of memory
available to the VM to see if that makes a difference.
From what I'm observing in #56, increasing the memory didn't help.
Further, it took a very long time to check out the jars-directory.
Seeing that the last successful runs happened on ubuntu1 and ubuntu3,
I've configured the job to only run there. The last failures have
happened on ubuntu2 and ubuntu4. I'm just testing out possible
low-effort solutions for now.
I've also scheduled another run.
--
Kristian
checkVMLevel:
junit-jdbc4:
junit-init-nocp:
junit-init:
emit-junit-classpath-jars:
[echo] Running with
jars:<https://builds.apache.org/job/Derby-10.9-suites.All/ws/10.9-head/jars/sane>
[echo] CLASSPATH (environment variable): ${env.CLASSPATH}
emit-junit-classpath:
junit-jdbc4-workhorse:
[junit] Running org.apache.derbyTesting.functionTests.tests.jdbc4._Suite
[junit] Tests run: 985, Failures: 0, Errors: 0, Time elapsed: 374.117 sec
junit-jmx:
[junit] Running
org.apache.derbyTesting.functionTests.tests.management._Suite
[junit] Tests run: 101, Failures: 0, Errors: 0, Time elapsed: 12.177 sec
junit-lowmem:
[junit] Running org.apache.derbyTesting.functionTests.tests.memory._Suite
Build timed out (after 400 minutes). Marking the build as failed.
Recording test results
