Build failed in Jenkins: JMeter » JMeter-trunk #46

[Apache Jenkins Server <je...@builds.apache.org>]

See <https://ci-builds.apache.org/job/JMeter/job/JMeter-trunk/46/display/redirect?page=changes>

Changes:

[Vladimir Sitnikov] Update org.sonarqube Gradle plugin to 3.0 (from 2.7.1)


------------------------------------------
Started by an SCM change
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on H43 (ubuntu) in workspace <https://ci-builds.apache.org/job/JMeter/job/JMeter-trunk/ws/>
[WS-CLEANUP] Deleting project workspace...
[WS-CLEANUP] Done
No credentials specified
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://gitbox.apache.org/repos/asf/jmeter.git # timeout=10
Fetching upstream changes from https://gitbox.apache.org/repos/asf/jmeter.git
 > git --version # timeout=10
 > git fetch --tags --progress -- https://gitbox.apache.org/repos/asf/jmeter.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision a0ed3e0e0c205257f25d359e2c7df91847f815c7 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f a0ed3e0e0c205257f25d359e2c7df91847f815c7 # timeout=10
Commit message: "Update org.sonarqube Gradle plugin to 3.0 (from 2.7.1)"
 > git rev-list --no-walk 769a2a1b68d4f963bd38c0f706997b2f5bb875b0 # timeout=10
Xvfb starting$ /usr/bin/Xvfb :0 -fbdir /home/jenkins/xvfb-46-..fbdir2178751380967416388
[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-trunk] $ <https://ci-builds.apache.org/job/JMeter/job/JMeter-trunk/ws/gradlew> "-Dorg.gradle.jvmargs=-Xmx512m -XX:MaxMetaspaceSize=512m" -PignoreSpotBugsFailures=true -Pspotbugs=true -PCI=true -Pcoverage=true --profile --no-daemon cleanTest check assemble
To honour the JVM settings for this build a new JVM will be forked. Please consider using the daemon: https://docs.gradle.org/6.6/userguide/gradle_daemon.html.
Daemon will be stopped at the end of the build stopping after processing
> Task :buildSrc:compileKotlin NO-SOURCE
> Task :buildSrc:compileJava NO-SOURCE
> Task :buildSrc:compileGroovy NO-SOURCE
> Task :buildSrc:pluginDescriptors
> Task :buildSrc:processResources NO-SOURCE
> Task :buildSrc:classes UP-TO-DATE
> Task :buildSrc:inspectClassesForKotlinIC

> Task :buildSrc:jar
:jar: No valid plugin descriptors were found in META-INF/gradle-plugins

> Task :buildSrc:assemble
> Task :buildSrc:autostyleKotlinCheck NO-SOURCE
> Task :buildSrc:batchtest:pluginDescriptors
> Task :buildSrc:batchtest:processResources
> Task :buildSrc:autostyleKotlinGradleCheck
> Task :buildSrc:autostyleCheck
> Task :buildSrc:compileTestKotlin NO-SOURCE
> Task :buildSrc:compileTestJava NO-SOURCE
> Task :buildSrc:compileTestGroovy NO-SOURCE
> Task :buildSrc:processTestResources NO-SOURCE
> Task :buildSrc:testClasses UP-TO-DATE
> Task :buildSrc:batchtest:autostyleKotlinCheck
> Task :buildSrc:validatePlugins FROM-CACHE
> Task :buildSrc:batchtest:autostyleKotlinGradleCheck
> Task :buildSrc:batchtest:autostyleCheck
> Task :buildSrc:batchtest:processTestResources NO-SOURCE
> Task :buildSrc:batchtest:compileKotlin
> Task :buildSrc:batchtest:compileJava NO-SOURCE
> Task :buildSrc:batchtest:classes
> Task :buildSrc:batchtest:inspectClassesForKotlinIC
> Task :buildSrc:batchtest:jar
> Task :buildSrc:batchtest:assemble
> Task :buildSrc:batchtest:compileTestKotlin NO-SOURCE
> Task :buildSrc:batchtest:pluginUnderTestMetadata
> Task :buildSrc:batchtest:compileTestJava NO-SOURCE
> Task :buildSrc:batchtest:testClasses UP-TO-DATE
> Task :buildSrc:batchtest:test NO-SOURCE
> Task :buildSrc:pluginUnderTestMetadata
> Task :buildSrc:test NO-SOURCE
> Task :buildSrc:check
> Task :buildSrc:build
> Task :buildSrc:batchtest:validatePlugins FROM-CACHE
> Task :buildSrc:batchtest:check
> Task :buildSrc:batchtest:build
checksum-dependency elapsed time: 1751ms, configurations processed: 21 (add -PchecksumTimingsPrint to print detailed timings)

See the profiling report at: file://<https://ci-builds.apache.org/job/JMeter/job/JMeter-trunk/ws/buildSrc/build/reports/profile/profile-2020-08-20-21-32-17.html>
A fine-grained performance profile is available: use the --scan option.
KO: verification of org.sonarsource.scanner.gradle:sonarqube-gradle-plugin:3.0 via cfca4a29d26468de
checksum-dependency elapsed time: 1783ms, configurations processed: 15 (add -PchecksumTimingsPrint to print detailed timings)

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'jmeter'.
> Checksum/PGP violations detected on resolving configuration :classpath
    No PGP signature (.asc file) found for artifact:
      org.sonarsource.scanner.gradle:sonarqube-gradle-plugin:3.0 (pgp=[], sha512=[AFC41AFD611214C500CACA4D826652E38D5DDD1BCF182D935AFFD2B5B8DF26650DFEB76E4C06C2D46593E1FB86BB4D093438E8E862666E64AB32FB4B6EFEA30D])
  
  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-trunk/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. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 38s

See the profiling report at: file://<https://ci-builds.apache.org/job/JMeter/job/JMeter-trunk/ws/reports/profile/profile-2020-08-20-21-32-14.html>
A fine-grained performance profile is available: use the --scan option.
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
Xvfb stopping
Archiving artifacts
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-trunk/ws/src/components/build/test-results/test/TEST-org.apache.jmeter.assertions.CompareAssertionSpec.xml> is 10 days old

Jenkins build is back to normal : JMeter » JMeter-trunk #47

[Apache Jenkins Server <je...@builds.apache.org>]

See <https://ci-builds.apache.org/job/JMeter/job/JMeter-trunk/47/display/redirect?page=changes>