[cdt-dev] Managed build JUnit failures

[Vivian Kong <vivkong@xxxxxxxxxx>]

I've noticed that the managed build JUnit tests aren't being run during the
4.0.2 builds and for 5.0.0 they were ran but with many errors and failures
(http://download.eclipse.org/tools/cdt/builds/5.0.0
/I.I200711051450/junits.html).

For 4.0.2, there's a Java core dump...

cdt-mbs-core:

init:

ui-test:

java-test:
     [echo] Running
org.eclipse.cdt.managedbuilder.tests.suite.AllManagedBuildTests. Result
file:
/opt/public/download-staging.priv/tools/cdt/releng/org.eclipse.cdt/all/org.eclipse.cdt.releng/results/I.I200711150800/testReports/org.eclipse.cdt.managedbuilder.tests.suite.AllManagedBuildTests.xml.
     [java] JVMDG217: Dump Handler is Processing Signal 11 - Please Wait.
     [java] JVMDG303: JVM Requesting Java core file
     [java] JVMDG304: Java core file written to
/opt/public/download-staging.priv/tools/cdt/releng/org.eclipse.cdt/all/org.eclipse.cdt.releng/results/eclipse/javacore.20071115.083856.4965.txt
     [java] JVMDG215: Dump Handler has Processed Exception Signal 11.
     [java] Java Result: 139

collect-results:
[junitreport] the file
/opt/public/download-staging.priv/tools/cdt/releng/org.eclipse.cdt/all/org.eclipse.cdt.releng/results/eclipse/org.eclipse.cdt.managedbuilder.tests.suite.AllManagedBuildTests.xml
 is empty.
[junitreport] This can be caused by the test JVM exiting unexpectedly
    [style] Warning: the task name <style> is deprecated. Use <xslt>
instead.
    [style] Transforming into
/opt/public/download-staging.priv/tools/cdt/releng/org.eclipse.cdt/all/org.eclipse.cdt.releng/results/I.I200711150800/testReports
   [concat] No existing resources and no nested text, doing nothing

For 5.0.0, I've tried running them inside Eclipse on Linux and they simply
fail (but they pass on Windows).

Doug, do you think I missed setting up something?  Causing them to fail?

Regards,

Vivian Kong
IBM Eclipse CDT
IBM Canada Toronto Lab
Phone: (905) 413-6067