Skip to content

fix(deps): update dependency org.apache.commons:commons-dbcp2 to v2.13.0 #2683

fix(deps): update dependency org.apache.commons:commons-dbcp2 to v2.13.0

fix(deps): update dependency org.apache.commons:commons-dbcp2 to v2.13.0 #2683

Triggered via pull request December 30, 2023 14:03
Status Failure
Total duration 6m 11s
Artifacts

main.yml

on: pull_request
Matrix Preparation
3s
Matrix Preparation
Error Prone (JDK 17)
3m 9s
Error Prone (JDK 17)
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

5 errors
Error Prone (JDK 17)
Could not determine the dependencies of task ':src:dist:compileJava'. > Could not resolve all dependencies for configuration ':src:dist:compileClasspath'. > Checksum/PGP violations detected on resolving configuration :src:dist:runtimeClasspath No trusted PGP keys are configured for group jakarta.transaction: jakarta.transaction:jakarta.transaction-api:1.3.3 (pgp=[47ef0ec60c210bc6dfaa5819b7ae15c15c321c44], 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 /home/runner/work/jmeter/jmeter/build/checksum/checksum.xml. You might add -PchecksumUpdate to update root checksum.xml file.
17, temurin, same hashcode, macos, America/New_York, tr_TR
Could not determine the dependencies of task ':src:dist:javadocAggregate'. > Could not resolve all dependencies for configuration ':src:protocol:jdbc:compileClasspath'. > Checksum/PGP violations detected on resolving configuration :src:protocol:jdbc:runtimeClasspath No trusted PGP keys are configured for group jakarta.transaction: jakarta.transaction:jakarta.transaction-api:1.3.3 (pgp=[47ef0ec60c210bc6dfaa5819b7ae15c15c321c44], 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 /Users/runner/work/jmeter/jmeter/build/checksum/checksum.xml. You might add -PchecksumUpdate to update root checksum.xml file.
21, corretto, windows, America/New_York, de_DE, stress JIT
Could not determine the dependencies of task ':src:dist:javadocAggregate'. > Could not resolve all dependencies for configuration ':src:protocol:jdbc:compileClasspath'. > Checksum/PGP violations detected on resolving configuration :src:protocol:jdbc:runtimeClasspath No trusted PGP keys are configured for group jakarta.transaction: jakarta.transaction:jakarta.transaction-api:1.3.3 (pgp=[47ef0ec60c210bc6dfaa5819b7ae15c15c321c44], 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 D:\a\jmeter\jmeter\build\checksum\checksum.xml. You might add -PchecksumUpdate to update root checksum.xml file.
11, corretto, same hashcode, windows, America/New_York, fr_FR, stress JIT
Could not determine the dependencies of task ':src:dist:javadocAggregate'. > Could not resolve all dependencies for configuration ':src:protocol:jdbc:compileClasspath'. > Checksum/PGP violations detected on resolving configuration :src:protocol:jdbc:runtimeClasspath No trusted PGP keys are configured for group jakarta.transaction: jakarta.transaction:jakarta.transaction-api:1.3.3 (pgp=[47ef0ec60c210bc6dfaa5819b7ae15c15c321c44], 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 D:\a\jmeter\jmeter\build\checksum\checksum.xml. You might add -PchecksumUpdate to update root checksum.xml file.
8, liberica, windows, UTC, tr_TR
Could not determine the dependencies of task ':src:dist:javadocAggregate'. > Could not resolve all dependencies for configuration ':src:protocol:jdbc:compileClasspath'. > Checksum/PGP violations detected on resolving configuration :src:protocol:jdbc:runtimeClasspath No trusted PGP keys are configured for group jakarta.transaction: jakarta.transaction:jakarta.transaction-api:1.3.3 (pgp=[47ef0ec60c210bc6dfaa5819b7ae15c15c321c44], 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 D:\a\jmeter\jmeter\build\checksum\checksum.xml. You might add -PchecksumUpdate to update root checksum.xml file.