See <https://ci-builds.apache.org/job/JMeter/job/JMeter%20s390x/167/display/redirect?page=changes>
Changes: [Vladimir Sitnikov] Fix log4j package warning on JMeter startup: WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated ... ------------------------------------------ Started by upstream project "JMeter/JMeter-trunk" build number 777 originally caused by: Started by GitHub push by vlsi Started by GitHub push by vlsi Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on jenkins-s390x-1 (s390x) in workspace <https://ci-builds.apache.org/job/JMeter/job/JMeter%20s390x/ws/> The recommended git tool is: NONE No credentials specified > git rev-parse --resolve-git-dir > <https://ci-builds.apache.org/job/JMeter/job/JMeter%20s390x/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.25.1' > git fetch --tags --force --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 cbdfd1ba435ad92b32c6538a5a433ac7dff9e024 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f cbdfd1ba435ad92b32c6538a5a433ac7dff9e024 # timeout=10 Commit message: "Fix log4j package warning on JMeter startup: WARN StatusConsoleListener The use of package scanning to locate plugins is deprecated ..." > git rev-list --no-walk 174ba3178f287d2984b1e53004e2c2cee1ffff16 # timeout=10 [Gradle] - Launching build. [JMeter s390x] $ "<https://ci-builds.apache.org/job/JMeter/job/JMeter%20s390x/ws/gradlew";> -Djava.awt.headless=true -PCI=true check createDist To honour the JVM settings for this build a single-use Daemon process will be forked. For more on this, please refer to https://docs.gradle.org/8.5/userguide/gradle_daemon.html#sec:disabling_the_daemon in the Gradle documentation. Daemon will be stopped at the end of the build Using the build cache is enabled, but no build caches are configured or enabled. Type-safe project accessors is an incubating feature. Path for java installation '/usr/lib/jvm/openjdk-11' (Common Linux Locations) does not contain a java executable > Configure project :build-logic-commons:gradle-plugin Directory '/home/jenkins/tools/java/latest15' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest1.8' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest1.6' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest1.7' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest14' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest13' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest12' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest20' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest1.4' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest23' (Maven Toolchains) used for java installations does not exist Path for java installation '/usr/local/asfpackages/java/adoptium-jdk-18.0.2.1+1' (Maven Toolchains) does not contain a java executable Directory '/home/jenkins/tools/java/latest24' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest10' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest16' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest1.5' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest1.9' (Maven Toolchains) used for java installations does not exist > Task > :build-logic-commons:gradle-plugin:checkKotlinGradlePluginConfigurationErrors > Task :build-logic-commons:gradle-plugin:generateExternalPluginSpecBuilders > UP-TO-DATE > Task :build-logic-commons:gradle-plugin:extractPrecompiledScriptPluginPlugins > UP-TO-DATE > Task :build-logic-commons:gradle-plugin:compilePluginsBlocks UP-TO-DATE > Task > :build-logic-commons:gradle-plugin:generatePrecompiledScriptPluginAccessors > UP-TO-DATE > Task :build-logic-commons:gradle-plugin:generateScriptPluginAdapters > UP-TO-DATE > Task :build-logic-commons:gradle-plugin:compileKotlin > Task :build-logic-commons:gradle-plugin:compileKotlin UP-TO-DATE > Task :build-logic-commons:gradle-plugin:compileJava NO-SOURCE > Task :build-logic-commons:gradle-plugin:pluginDescriptors UP-TO-DATE > Task :build-logic-commons:gradle-plugin:processResources UP-TO-DATE > Task :build-logic-commons:gradle-plugin:classes UP-TO-DATE > Task :build-logic-commons:gradle-plugin:jar UP-TO-DATE Path for java installation '/usr/lib/jvm/openjdk-11' (Common Linux Locations) does not contain a java executable > Configure project :build-logic:basics Directory '/home/jenkins/tools/java/latest24' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest10' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest13' (Maven Toolchains) used for java installations does not exist Path for java installation '/usr/local/asfpackages/java/adoptium-jdk-18.0.2.1+1' (Maven Toolchains) does not contain a java executable Directory '/home/jenkins/tools/java/latest1.7' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest1.4' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest1.6' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest20' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest16' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest1.9' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest23' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest15' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest1.8' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest14' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest12' (Maven Toolchains) used for java installations does not exist Directory '/home/jenkins/tools/java/latest1.5' (Maven Toolchains) used for java installations does not exist checksum-dependency elapsed time: 12376ms, configurations processed: 18 (add -PchecksumTimingsPrint to print detailed timings) checksum-dependency elapsed time: 22287ms, configurations processed: 3 SHA-512 computation time: 62ms (goes in parallel, it might exceed wall-clock time), files processed: 13, processed: 4MiB, skipped: 98MiB PGP signature resolution time: 5323ms (wall-clock), resolution requests: 2, signatures resolved: 63 PGP key resolution time: 3448ms (wall-clock), resolution requests: 2, download time: 0ms (goes in parallel, it might exceed wall-clock time), keys downloaded: 0 PGP signature verification time: 3411ms (goes in parallel, it might exceed wall-clock time), files processed: 63, processed: 98MiB, skipped: 0MiB FAILURE: Build failed with an exception. * What went wrong: A problem occurred configuring root project 'jmeter'. > Could not determine the dependencies of null. > Checksum/PGP violations detected on resolving configuration :classpath Actual checksum is [EC2200E5A5A70F5C64744F6413A546F5E4979B3FB1649B02756FF035D36DDE31170EAADC70842230296B60896F04877270C26B40415736299AEF44AC16C5811C], however expected one of [37A13B129F3536A53F2A553151A53997DA6DE7CE4D7231EFEEFD26A68C92BE309666F2EE1F527D3B8C38BC6ADDC9FCCBBDD0D134759FD88667976B0CFF842435]: xerces:xercesImpl:2.9.1 (pgp=[], sha512=[EC2200E5A5A70F5C64744F6413A546F5E4979B3FB1649B02756FF035D36DDE31170EAADC70842230296B60896F04877270C26B40415736299AEF44AC16C5811C]) There might be more checksum violations, however, current configuration specifies the build to fail on the first violation. You might use the following properties: * -PchecksumIgnore temporary disables checksum-dependency-plugin (e.g. to try new dependencies) * -PchecksumUpdate updates checksum.xml and it will fail after the first violation so you can review the diff * -PchecksumUpdateAll (insecure) updates checksum.xml with all the new discovered checksums * -PchecksumFailOn=build_finish (insecure) It will postpone the failure till the build finish It will collect all the violations, however untrusted code might be executed (e.g. from a plugin) You can find updated checksum.xml file at <https://ci-builds.apache.org/job/JMeter/job/JMeter%20s390x/ws/build/checksum/checksum.xml.> You might add -PchecksumUpdate to update root checksum.xml file. * Try: > Run with --stacktrace option to get the stack trace. > Run with --info or --debug option to get more log output. > Get more help at https://help.gradle.org. BUILD FAILED in 3m 33s 10 actionable tasks: 1 executed, 9 up-to-date Publishing build scan... https://ge.apache.org/s/2wnafzsy7bkci Build step 'Invoke Gradle script' changed build result to FAILURE Build step 'Invoke Gradle script' marked build as failure
