jdk can be good point, pass build use: Java version: 1.8.0_241, vendor: Oracle Corporation, runtime: /usr/local/asfpackages/java/jdk1.8.0_241/jre failed has: Java version: 1.8.0_252, vendor: Oracle Corporation, runtime: /usr/local/asfpackages/java/openjdk-8u252-b09/jre
on mac os with: Java version: 1.8.0_252, vendor: AdoptOpenJDK, runtime: /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre build pass successful pon., 27 lip 2020 o 08:31 Robert Scholte <rfscho...@apache.org> napisał(a): > My bad, it is indeed the Ubuntu that is failing. > It might be caused be JDK-8177809[1] > IIRC when using Path instead of File you won't have this issue. > > Robert > > [1] https://bugs.openjdk.java.net/browse/JDK-8177809 > > > On 27-7-2020 07:31:41, Christian Stein <sormu...@gmail.com> wrote: > Hi, > > Why do you think it's the Windows node, Robert? > > For me, it [1] says 5 times: linux-jdk8-m3.6.x_build > The file separator chars displayed in the log file also points to a Linux > node: > > > > > [INFO] The post-build script did not succeed. assert buildLog.text =~ > > /(?i) Archive .*${sourcesJarFileName} is uptodate/ > > | | | | > > | | | > > empty-source-directory-1.0-SNAPSHOT-sources.jar > > | | java.util.regex.Matcher[pattern=(?i) Archive > > .*empty-source-directory-1.0-SNAPSHOT-sources.jar is uptodate > > region=0,44353 lastmatch=] > > | Picked up JAVA_TOOL_OPTIONS: > > > -Dmaven.ext.class.path="/home/jenkins/jenkins-slave/workspace/n-box_maven-source-plugin_master@3 > > @2@tmp/withMaven42d62564/pipeline-maven-spy.jar" > > > -Dorg.jenkinsci.plugins.pipeline.maven.reportsFolder="/home/jenkins/jenkins-slave/workspace/n-box_maven-source-plugin_master@3 > > @2@tmp/withMaven42d62564" > > > The underlying reason for the failure is not clear to me. > IIUC, the log says a new -sources.jar was created for an IT > named MSOURCES-95. > But the expectation is, that an "uptodate" check prevents a recreation of > the -sources.jar file? > > Cheers, > Christian > > [1] > > https://builds.apache.org/blue/organizations/jenkins/maven-box%2Fmaven-source-plugin/activity > > > > On Sun, Jul 26, 2020 at 9:56 PM Robert Scholte wrote: > > > Anybody willing to analyze why this plugin is broken for a while?[1] > > It look like there hasn't been a commit since the last success (recent > > changes only show commits on our Jenkins files) > > > > All other master are currently stable.[2] > > > > thanks, > > Robert > > > > [1] > > > https://builds.apache.org/job/maven-box/job/maven-source-plugin/job/master/ > > [2] > > > https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/dist-tool-master-jobs.html > > > > > -- Sławomir Jaranowski