See <https://ci-builds.apache.org/job/JMeter/job/JMeter-analysis/245/display/redirect?page=changes>
Changes: [Bruno Demion] Add the 5.4.2 release ------------------------------------------ Started by upstream project "JMeter/JMeter-trunk" build number 356 originally caused by: Started by GitHub push by asfgit Started by GitHub push by asfgit Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H41 (ubuntu) in workspace <https://ci-builds.apache.org/job/JMeter/job/JMeter-analysis/ws/> [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Done The recommended git tool is: NONE No credentials specified > git rev-parse --resolve-git-dir > <https://ci-builds.apache.org/job/JMeter/job/JMeter-analysis/ws/.git> # > timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/apache/jmeter.git # > timeout=10 Fetching upstream changes from https://github.com/apache/jmeter.git > git --version # timeout=10 > git --version # 'git version 2.17.1' > git fetch --tags --progress -- https://github.com/apache/jmeter.git > +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 Checking out Revision f2f4a0e7fbc0b527929e0d1e7235d62175abf122 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f f2f4a0e7fbc0b527929e0d1e7235d62175abf122 # timeout=10 Commit message: "Add the 5.4.2 release" > git rev-list --no-walk 0551e4cef9c693fb1661580a3abb212763104a9d # timeout=10 Xvfb starting$ /usr/bin/Xvfb :0 -fbdir <https://ci-builds.apache.org/job/JMeter/job/JMeter-analysis/ws/.xvfb-245-..fbdir382148171009539752> [EnvInject] - Executing scripts and injecting environment variables after the SCM step. [EnvInject] - Injecting as environment variables the properties content SONAR_HOST_URL=https://sonarcloud.io [EnvInject] - Variables injected successfully. [EnvInject] - Mask passwords that will be passed as build parameters. [Gradle] - Launching build. [JMeter-analysis] $ <https://ci-builds.apache.org/job/JMeter/job/JMeter-analysis/ws/gradlew> "-Dorg.gradle.jvmargs=-Xmx1g -XX:MaxMetaspaceSize=512m" -PignoreSpotBugsFailures=true -Pspotbugs=true -PCI=true -Pcoverage=true --profile --no-daemon cleanTest check assemble sonarqube --exclude-task :src:dist:javadocAggregate <https://ci-builds.apache.org/job/JMeter/job/JMeter-analysis/ws/gradlew>: 185: exec: /home/jenkins/tools/java/latest11/bin/java: Exec format error Build step 'Invoke Gradle script' changed build result to FAILURE Build step 'Invoke Gradle script' marked build as failure Xvfb stopping Recording test results ERROR: Step ?Publish JUnit test result report? failed: Test reports were found but none of them are new. Did leafNodes run? For example, <https://ci-builds.apache.org/job/JMeter/job/JMeter-analysis/ws/src/components/build/test-results/test/TEST-org.apache.jmeter.assertions.CompareAssertionSpec.xml> is 9 days 15 hr old
