I've swapped it back to the fleet for now.
If we were to use the master node, I'd want to add a label to the java11
jobs so that they are the only ones which run on it (especially since other
jobs may rely on resources not available on master). I could take a look at
actually doing that sometime ne
Hi Torben,
thanks for testing it out. As a curiosity, is the build back to use the
fleet, or is it using the
build server local hardware? At 50 minutes it's sure slow, but still beats
a failing build.
Cheers
Andrea
On Wed, Oct 16, 2019 at 7:06 PM Torben Barsballe <
tbarsba...@federal.planet.com>
Following up on the discussion in the PMC meeting:
- Trying the geotools-java11 build with Java 11.0.4 failed in much of
the same way as Java 11.0.3:
https://build.geoserver.org/job/geotools-java11/511/consoleFull
- Running the geotools-java11 build on the master node passed:
https:
Hi Andrea,
using Java 11 (OpenJDK 11 from AdoptOpenJDK) I get the same results as
you.
I have isolated this two errors as the origin:
java.lang.NullPointerException
at
java.xml/com.sun.org.apache.xerces.internal.dom.ParentNode.nodeLi
stGetLength(ParentNode.java:697)
