See
<https://ci-builds.apache.org/job/JMeter/job/JMeter-trunk/504/display/redirect?page=changes>
Changes:
[Vladimir Sitnikov] chore: bump Gradle to 8.1.1
[Vladimir Sitnikov] chore: factor build-logic so it is easier to reuse
------------------------------------------
[...truncated 971.20 KB...]
Checksum/PGP violations detected on resolving configuration
:src:protocol:mongodb:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
Checksum/PGP violations detected on resolving configuration
:src:components:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
Checksum/PGP violations detected on resolving configuration
:src:generator:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
Checksum/PGP violations detected on resolving configuration
:src:protocol:jdbc:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
Checksum/PGP violations detected on resolving configuration
:src:protocol:http:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
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.
==============================================================================
18: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':src:protocol:jms:spotbugsMain'.
> Checksum/PGP violations detected on resolving configuration
> :src:protocol:jms:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
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.
==============================================================================
19: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':src:protocol:mongodb:spotbugsMain'.
> Checksum/PGP violations detected on resolving configuration
> :src:protocol:jms:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
Checksum/PGP violations detected on resolving configuration
:src:launcher:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
Checksum/PGP violations detected on resolving configuration
:src:protocol:mongodb:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
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.
==============================================================================
20: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':src:protocol:jdbc:spotbugsMain'.
> Checksum/PGP violations detected on resolving configuration
> :src:protocol:jms:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
Checksum/PGP violations detected on resolving configuration
:src:launcher:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
Checksum/PGP violations detected on resolving configuration
:src:protocol:mongodb:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
Checksum/PGP violations detected on resolving configuration
:src:components:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
Checksum/PGP violations detected on resolving configuration
:src:generator:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
Checksum/PGP violations detected on resolving configuration
:src:protocol:jdbc:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
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.
==============================================================================
21: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':src:launcher:spotbugsMain'.
> Checksum/PGP violations detected on resolving configuration
> :src:protocol:jms:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
Checksum/PGP violations detected on resolving configuration
:src:launcher:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
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.
==============================================================================
22: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':src:components:spotbugsMain'.
> Checksum/PGP violations detected on resolving configuration
> :src:protocol:jms:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
Checksum/PGP violations detected on resolving configuration
:src:launcher:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
Checksum/PGP violations detected on resolving configuration
:src:protocol:mongodb:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
Checksum/PGP violations detected on resolving configuration
:src:components:spotbugs
Trusted PGP keys for group jaxen are
[4daded739cdf2cd0e48e0ec44044edf1bb73efea], however artifact is signed by
[ca491704d613780d2bee00f2c6fc46eb51cf569c] only:
jaxen:jaxen:1.2.0 (pgp=[ca491704d613780d2bee00f2c6fc46eb51cf569c],
sha512=[computation skipped])
Trusted PGP keys for group org.slf4j are
[475f3b8e59e6e63aa78067482c7b12f2a511e325], however artifact is signed by
[60200ac4ae761f1614d6c46766d68daa073be985] only:
org.slf4j:slf4j-api:2.0.0
(pgp=[60200ac4ae761f1614d6c46766d68daa073be985], sha512=[computation skipped])
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.
==============================================================================
* Get more help at https://help.gradle.org
BUILD FAILED in 10m 9s
409 actionable tasks: 378 executed, 1 from cache, 30 up-to-date
See the profiling report at:
file://<https://ci-builds.apache.org/job/JMeter/job/JMeter-trunk/ws/build/reports/profile/profile-2023-04-27-11-28-15.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: No test report files
were found. Configuration error?
