Community
Participate
Working Groups
In a recent build, the unit tests apparently finished, but before they were transformed to HTML, the process timed out. This left the "results" page kind of confusing ... it showed the results summary table, but a link to any individual test results (the HTML version) was a 404/not found. And indeed, on build server, there were XML versions (indicating the test ran ok) but no HTML version (indicating the XSL transform did not complete). The antBuilderOutput.log had "high level" time out error message: 791463 runTestEclipse: 791464 [echo] testTarget: all 791465 [echo] Running junits 791466 [echo] eclipse.launcher: /shared/webtools/basebuilders/R36_RC4/org.eclipse.releng.basebuilder/plugins/org.eclipse.equinox.launcher.jar 791467 [unit-test-masterprocess] Timeout: killed the sub-process 791468 [unit-test-masterprocess] at org.apache.tools.ant.taskdefs.Java.fork(Java.java:787) 791469 [unit-test-masterprocess] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:211) 791470 [unit-test-masterprocess] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:132) 791471 [unit-test-masterprocess] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:105) 791472 [unit-test-masterprocess] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) ... It appears 3 individual tests timed out (but hard to tell right off which ones). So ... I think just bad timing we hit the overall limit when we did. A couple of improvements could be made in future perhaps. a) overall timeout applies to only tests ... move the "transforms" out to "post processing" step (postRunTestEclipse). b) improve error messaging, so when an overall timeout occurs, to reflect some message about that in the test results pages/summaries. I suspect, though, this is an pretty exceptional case ... unless there is something else causing the overall time out (e.g. some infrastructure problem) in which case that'll need attention in its own right.
