Somehow WTP's CI builds, which are built against the Platform's latest I-builds to help find these kinds of problems right when they start, stopped building daily during M1. Once I cleared the blockage, every last one of our builds started failing, even the ones where the job configuration and code base hadn't been touched. I've been exploring solutions in
https://git.eclipse.org/r/c/jsdt/webtools.jsdt/+/170607, switching to the newest Maven and Tycho since we were using a really old version that didn't understand not to use -bootclasspath, but we're still blocked running UI tests. Mostly I've figured out the various problems that are our fault along with setting our target-platform-configuration to be JavaSE-11, but I've not been able to solve a problem invoking tycho-surefire that's left me with this curious diagnostic output. The majority of our CI build failures look like this, or have a null instead of a value from our toolchains file if I leave the test bundle's pom's useJDK property at the SYSTEM default--even though the whole thing is already being run with Java 11.
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:2.1.0-SNAPSHOT:test (default-test) on project org.eclipse.wst.jsdt.debug.core.tests: An unexpected error occurred while launching the test runtime (process returned error code 127). The process logfile /jobs/genie.webtools/webtools-jsdt-gerrit_master/workspace/tests/org.eclipse.wst.jsdt.debug.core.tests/target/work/data/.metadata/.log might contain further details. Command-line used to launch the sub-process was /shared/common/java/oracle/jdk-11_x64-latest/bin/java -Dosgi.noShutdown=false -Dosgi.os=linux -Dosgi.ws=gtk -Dosgi.arch=x86_64 -Dorg.osgi.framework.bundle.parent=ext -Dosgi.clean=true -jar /jobs/genie.webtools/webtools-jsdt-gerrit_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 -debug -consolelog -data /jobs/genie.webtools/webtools-jsdt-gerrit_master/workspace/tests/org.eclipse.wst.jsdt.debug.core.tests/target/work/data -install /jobs/genie.webtools/webtools-jsdt-gerrit_master/workspace/tests/org.eclipse.wst.jsdt.debug.core.tests/target/work -configuration /jobs/genie.webtools/webtools-jsdt-gerrit_master/workspace/tests/org.eclipse.wst.jsdt.debug.core.tests/target/work/configuration -application org.eclipse.tycho.surefire.osgibooter.uitest -testproperties /jobs/genie.webtools/webtools-jsdt-gerrit_master/workspace/tests/org.eclipse.wst.jsdt.debug.core.tests/target/surefire.properties in working directory /jobs/genie.webtools/webtools-jsdt-gerrit_master/workspace/tests/org.eclipse.wst.jsdt.debug.core.tests -> [Help 1]
The java executable is actually executable by the builder user ID, and yet error 127 points to it either not being there at all or not executable by the builder user ID. I've already spent an unhealthy amount of time on this--does anyone have any ideas I can try to get our project past this blocker?
