Skip to content

fix(deps): update dependency dnsjava:dnsjava to v3 #2808

fix(deps): update dependency dnsjava:dnsjava to v3

fix(deps): update dependency dnsjava:dnsjava to v3 #2808

Triggered via pull request September 21, 2024 10:18
Status Failure
Total duration 8m 48s
Artifacts

main.yml

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

Annotations

5 errors and 5 warnings
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 Trusted PGP keys for group dnsjava are [3e1ac64f4e34e290503c90323449ec3ac2efe8aa], however artifact is signed by [e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9] only: dnsjava:dnsjava:3.6.2 (pgp=[e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9], 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, liberica, windows, Pacific/Chatham, fr_FR
Could not determine the dependencies of task ':src:dist:javadocAggregate'. > Could not resolve all dependencies for configuration ':src:protocol:http:compileClasspath'. > Checksum/PGP violations detected on resolving configuration :src:protocol:http:runtimeClasspath Trusted PGP keys for group dnsjava are [3e1ac64f4e34e290503c90323449ec3ac2efe8aa], however artifact is signed by [e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9] only: dnsjava:dnsjava:3.6.2 (pgp=[e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9], 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.
21, liberica, same hashcode, windows, Pacific/Chatham, tr_TR
Could not determine the dependencies of task ':src:dist:javadocAggregate'. > Could not resolve all dependencies for configuration ':src:protocol:http:compileClasspath'. > Checksum/PGP violations detected on resolving configuration :src:protocol:http:runtimeClasspath Trusted PGP keys for group dnsjava are [3e1ac64f4e34e290503c90323449ec3ac2efe8aa], however artifact is signed by [e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9] only: dnsjava:dnsjava:3.6.2 (pgp=[e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9], 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.
21, microsoft, windows, America/New_York, tr_TR
Could not determine the dependencies of task ':src:dist:javadocAggregate'. > Could not resolve all dependencies for configuration ':src:protocol:http:compileClasspath'. > Checksum/PGP violations detected on resolving configuration :src:protocol:http:runtimeClasspath Trusted PGP keys for group dnsjava are [3e1ac64f4e34e290503c90323449ec3ac2efe8aa], however artifact is signed by [e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9] only: dnsjava:dnsjava:3.6.2 (pgp=[e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9], 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.
17, microsoft, macos, UTC, tr_TR, stress JIT
Could not determine the dependencies of task ':src:dist:javadocAggregate'. > Could not resolve all dependencies for configuration ':src:protocol:http:compileClasspath'. > Checksum/PGP violations detected on resolving configuration :src:protocol:http:runtimeClasspath Trusted PGP keys for group dnsjava are [3e1ac64f4e34e290503c90323449ec3ac2efe8aa], however artifact is signed by [e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9] only: dnsjava:dnsjava:3.6.2 (pgp=[e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9], 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.
Error Prone (JDK 17)
The following actions use a deprecated Node.js version and will be forced to run on node20: burrunan/gradle-cache-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
17, liberica, windows, Pacific/Chatham, fr_FR
The following actions use a deprecated Node.js version and will be forced to run on node20: burrunan/gradle-cache-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
21, liberica, same hashcode, windows, Pacific/Chatham, tr_TR
The following actions use a deprecated Node.js version and will be forced to run on node20: burrunan/gradle-cache-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
21, microsoft, windows, America/New_York, tr_TR
The following actions use a deprecated Node.js version and will be forced to run on node20: burrunan/gradle-cache-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
17, microsoft, macos, UTC, tr_TR, stress JIT
The following actions use a deprecated Node.js version and will be forced to run on node20: burrunan/gradle-cache-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/