Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Unable to launch test runtime with tycho-surefire 2.1
Thanks for the idea, but that doesn't seem to be the issue--all headless tests still run fine.

One thing I did skip over is that other WTP project builds are constructing a test application command line with "null" instead of an entry from the specified toolchains or the JRE running the build. That's a bug, right?

[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:2.1.0-SNAPSHOT:test (default-test) on project org.eclipse.wst.xml.ui.tests: An unexpected error occurred while launching the test runtime (process returned error code 127). Command-line used to launch the sub-process was null -Dosgi.noShutdown=false -Dosgi.os=linux -Dosgi.ws=gtk -Dosgi.arch=x86_64 -Dosgi.clean=true -jar /jobs/genie.webtools/webtools-sourceediting_master/workspace/.repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.6.0.v20200915-1508/org.eclipse.equinox.launcher-1.6.0.v20200915-1508.jar -data /jobs/genie.webtools/webtools-sourceediting_master/workspace/xml/tests/org.eclipse.wst.xml.ui.tests/target/work/data -install /jobs/genie.webtools/webtools-sourceediting_master/workspace/xml/tests/org.eclipse.wst.xml.ui.tests/target/work -configuration /jobs/genie.webtools/webtools-sourceediting_master/workspace/xml/tests/org.eclipse.wst.xml.ui.tests/target/work/configuration -application org.eclipse.tycho.surefire.osgibooter.uitest -testproperties /jobs/genie.webtools/webtools-sourceediting_master/workspace/xml/tests/org.eclipse.wst.xml.ui.tests/target/surefire.properties in working directory /jobs/genie.webtools/webtools-sourceediting_master/workspace/xml/tests/org.eclipse.wst.xml.ui.tests -> [Help 1]

On Tue, Oct 27, 2020 at 5:38 AM Jeff MAURY <jeffmaury@xxxxxxxxxxxxx> wrote:
I don't see the Java11+ specific flags being set when launching the runtime.
In JBoss Tools, we explicitly add --add-modules=ALL-SYSTEM

On Mon, Oct 26, 2020 at 1:38 AM Nitin Dahyabhai <thatnitind@xxxxxxxxx> wrote:
I'd have to use the MAVEN_OPTS variable to try something like that, but as one would hope, the ports are firewalled off and prevent that. Besides, it's what's happening in the test application that's of more interest than the Maven process itself--why is it returning an error code and not running the UI tests. There are no surefire-reports generated for that test bundle, so it's still a mystery to me.

On Sat, Oct 24, 2020 at 3:57 PM Mickael Istria <mistria@xxxxxxxxxx> wrote:
If the application is starting, at this point what might be best is to enable debug to find out why and how it's interrupted.
Try using the `-DdebugPort=8000` flag and then connect to your test from the IDE using a remote Java application launch config.
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tycho-user


--
Regards,
Nitin Dahyabhai
Eclipse WTP PMC
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tycho-user


--
Jeff MAURY


"Legacy code" often differs from its suggested alternative by actually working and scaling.
 - Bjarne Stroustrup

http://www.jeffmaury.com
http://riadiscuss.jeffmaury.com
http://www.twitter.com/jeffmaury
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tycho-user


--
Regards,
Nitin Dahyabhai
Eclipse WTP PMC

Back to the top