I found the issue. It was broken before too, but the old piping
construct just ignored the error (but it was still printed). Fixed by
making sure the bootcycle-build directory exists before calling the
bootcycle build.
Bug: https://bugs.openjdk.java.net/browse/JDK-8221996
Webrev: http://cr.openjdk.java.net/~erikj/8221996/webrev.01/
/Erik
On 2019-04-04 11:40, Erik Joelsson wrote:
It's not just you. I see it in our CI as well. It was caused by my
change https://bugs.openjdk.java.net/browse/JDK-8221764 Will look into
it.
/Erik
On 2019-04-04 11:35, Andrew Haley wrote:
This is jdk-jdk, 54423:6c0ab8bd8da5
Building JVM variant 'server' with features 'aot cds cmsgc compiler1
compiler2 dtrace epsilongc g1gc graal jfr jni-check jvmci jvmti
management nmt parallelgc serialgc services shenandoahgc vm-structs'
Boot cycle build step 2: Building a new JDK image using previously
built image
/usr/bin/tee:
/home/aph/jdk-jdk/build/linux-aarch64-server-slowdebug/bootcycle-build/build.log:
No such file or directory
Building target 'product-images' in configuration
'linux-aarch64-server-slowdebug'
gmake[3]: *** [main] Error 1
gmake[2]: *** [bootcycle-images] Error 2
Is this just me? Has anyone else seen it?
