|
alternatively, the printed testcase times dont print the teardown time, and it is those times that are causing the total elapsed time to overrun. The junit test runner is correctly killing a test run that is taking longer than specified
extended the test run times, appears to work now
|
||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Major
Ant <start> tests failing on Hudson
Look at this trace as an example: each tests takes little time, but the test run took 240s, 4 minutes.
[sf-junit] Testcase: testNoParams took 0.039 sec
[sf-junit] Testcase: testNoFailure took 0.019 sec
[sf-junit] Testcase: testEmptyApplication took 0.022 sec
[sf-junit] Testcase: testAnonApplication took 0.031 sec
[sf-junit] Testcase: testDatalessApplication took 0.097 sec
[sf-junit] Testcase: testBadFile took 0.01 sec
[sf-junit] Testcase: testBadHost took 0.01 sec
[sf-junit] Testcase: testRunFile took 1.409 sec
[sf-junit] Testcase: testResource took 1.339 sec
[sf-junit] Testcase: testInline took 1.334 sec
[sf-junit] Testcase: testStackTrace took 1.288 sec
[sf-junit] Testcase: testSubdir took 0.983 sec
[sf-junit] Testcase: testAssertions took 1.005 sec
[sf-junit] Testcase: testEmptyPropertyFile took 0.042 sec
[sf-junit] Testcase: testMissingNonOptionalPropertyFile took 0.027 sec
[sf-junit] Testcase: testMissingOptionalPropertyFile took 1.761 sec
[sf-junit] Testcase: testValidPropertyFile took 1.67 sec
[sf-junit] Testsuite: org.smartfrog.tools.ant.test.system.StartTest
[sf-junit] Tests run: 16, Failures: 0, Errors: 0, Time elapsed: 239.273 sec
[sf-junit]
For some reason the VM is being suspended for minutes at a time, usually in the ant task tests. If it happens within a test, timeouts kick in and the tests fail. If it happens outside, the build passes, but the timing problem is still there.