Gradle build failed: see console output for details

Gradle build failed: see console output for details

Gradle build failed: see console output for details

The operation was canceled.

The strategy configuration was canceled because "dafny-nightly-test-vectors-java.testJava.TestVectors_11_ubuntu-22_" failed

The operation was canceled.

The strategy configuration was canceled because "dafny-nightly-test-vectors-java.testJava.TestVectors_11_ubuntu-22_" failed

The operation was canceled.

The strategy configuration was canceled because "dafny-nightly-test-vectors-java.testJava.TestVectors_11_ubuntu-22_" failed

The operation was canceled.

The strategy configuration was canceled because "dafny-nightly-test-vectors-java.testJava.TestVectors_11_ubuntu-22_" failed

The operation was canceled.

The strategy configuration was canceled because "dafny-nightly-net.testDotNet.DynamoDbEncryption_6_0__2" failed

The operation was canceled.

The strategy configuration was canceled because "dafny-nightly-test-vectors-net.testDotNet.TestVectors_6_0_x_ubuntu-" failed

The operation was canceled.

The strategy configuration was canceled because "dafny-nightly-test-vectors-java.testJava.TestVectors_11_ubuntu-22_" failed

The operation was canceled.

The strategy configuration was canceled because "dafny-nightly-test-vectors-java.testJava.TestVectors_11_ubuntu-22_" failed

The operation was canceled.

The strategy configuration was canceled because "dafny-nightly-test-vectors-java.testJava.TestVectors_11_ubuntu-22_" failed

The operation was canceled.

The strategy configuration was canceled because "dafny-nightly-net.testDotNet.DynamoDbEncryption_6_0__2" failed

Process completed with exit code 2.

Process completed with exit code 2.

Process completed with exit code 2.

Process completed with exit code 2.

Process completed with exit code 2.

Process completed with exit code 2.

Process completed with exit code 2.

The operation was canceled.

The strategy configuration was canceled because "dafny-nightly-java.testJava.DynamoDbEncryption_17_mac" failed

The operation was canceled.

The strategy configuration was canceled because "dafny-nightly-java.testJava.DynamoDbEncryption_17_mac" failed

The operation was canceled.

The strategy configuration was canceled because "dafny-nightly-java.testJava.DynamoDbEncryption_17_mac" failed

Failed to restore v8-gradle|Linux|dafny nightly-testDotNet[7206fa0e0cedb6913d76412c6501ba2d]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to restore v8-gradle|Linux|dafny nightly-testJava[cf83f91084cb2aa9bb0f7264c9bc0b4c]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to restore v8-gradle|Linux|dafny nightly-testDotNet[a7a5bf8db14f32543239f51f99b1fdf5]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!

Treating docker as a formula. For the cask, use homebrew/cask/docker or specify the `--cask` flag. To silence this message, use the `--formula` flag.

HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!

Failed to restore v8-gradle|Linux|dafny nightly-testJava[d64029b32e987bd2d2c427a8bd87afe1]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to restore v8-gradle|Linux|dafny nightly-testJava[7bd2eedc32a9de7e14eee65e42820c89]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to restore v8-gradle|Linux|dafny nightly-testJava[bad853adad5c7049a0ab2b343ed9eb2b]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to restore v8-gradle|macOS|dafny nightly-testDotNet[e99ab70d0c434fd2e6aa07a1549c8f88]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!

Treating docker as a formula. For the cask, use homebrew/cask/docker or specify the `--cask` flag. To silence this message, use the `--formula` flag.

HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!

HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!

Treating docker as a formula. For the cask, use homebrew/cask/docker or specify the `--cask` flag. To silence this message, use the `--formula` flag.

HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!

HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!

Treating docker as a formula. For the cask, use homebrew/cask/docker or specify the `--cask` flag. To silence this message, use the `--formula` flag.

HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!

HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!

Treating docker as a formula. For the cask, use homebrew/cask/docker or specify the `--cask` flag. To silence this message, use the `--formula` flag.

HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!

Unhandled error in Gradle post-action - job will continue: Error: EBUSY: resource busy or locked, unlink 'C:\Users\runneradmin\.gradle\caches\modules-2\files-2.1\org.jetbrains.kotlin\kotlin-stdlib-common\1.9.0\cd65c21cfd1eec4d44ef09f9f52b6d9f8a720636\kotlin-stdlib-common-1.9.0.jar'

Failed to delete C:\Users\runneradmin\.gradle\caches\modules-2\files-2.1\org.jetbrains.kotlin\kotlin-stdlib-common\1.9.0\cd65c21cfd1eec4d44ef09f9f52b6d9f8a720636, which will impact caching. It is likely locked by another process. Output of 'jps -ml': 1920 sun.tools.jps.Jps -lm 4616 sun.tools.jps.Jps -lm 4744 sun.tools.jps.Jps -lm 6792 sun.tools.jps.Jps -lm 6920 -- process information unavailable 4364 sun.tools.jps.Jps -lm 5524 sun.tools.jps.Jps -lm 2200 sun.tools.jps.Jps -lm 4632 -- process information unavailable 2972 sun.tools.jps.Jps -lm 4124 -- process information unavailable 5020 sun.tools.jps.Jps -lm 5916 -- process information unavailable 5536 sun.tools.jps.Jps -lm 1316 -- process information unavailable 2468 sun.tools.jps.Jps -lm 1964 sun.tools.jps.Jps -lm 3116 sun.tools.jps.Jps -lm 556 sun.tools.jps.Jps -lm 6572 sun.tools.jps.Jps -lm 4404 sun.tools.jps.Jps -lm 1208 sun.tools.jps.Jps -lm 6712 sun.tools.jps.Jps -lm 3900 sun.tools.jps.Jps -lm 5308 sun.tools.jps.Jps -lm 5820 -- process information unavailable 7360 sun.tools.jps.Jps -lm 1348 sun.tools.jps.Jps -lm 3012 sun.tools.jps.Jps -lm 3140 -- process information unavailable 4932 sun.tools.jps.Jps -lm 6856 -- process information unavailable 5196 sun.tools.jps.Jps -lm 7372 sun.tools.jps.Jps -lm 3792 sun.tools.jps.Jps -lm 2900 sun.tools.jps.Jps -lm 3924 org.gradle.launcher.daemon.bootstrap.GradleDaemon 8.3 724 sun.tools.jps.Jps -lm 2904 sun.tools.jps.Jps -lm 3416 -- process information unavailable 604 sun.tools.jps.Jps -lm 7388 sun.tools.jps.Jps -lm 3808 -- process information unavailable 1892 sun.tools.jps.Jps -lm 4580 sun.tools.jps.Jps -lm 7396 sun.tools.jps.Jps -lm 1128 sun.tools.jps.Jps -lm 4844 sun.tools.jps.Jps -lm 4084 sun.tools.jps.Jps -lm 6516 -- process information unavailable 4600 -- process information unavailable

Unhandled error in Gradle post-action - job will continue: Error: EBUSY: resource busy or locked, unlink 'C:\Users\runneradmin\.gradle\wrapper\dists\gradle-8.3-bin\dxjbbhstwasg8cbags9q7cvli\gradle-8.3\lib\agents\gradle-instrumentation-agent-8.3.jar'

Failed to delete C:\Users\runneradmin\.gradle\wrapper\dists\gradle-8.3-bin\dxjbbhstwasg8cbags9q7cvli, which will impact caching. It is likely locked by another process. Output of 'jps -ml': 1620 sun.tools.jps.Jps -lm 3924 org.gradle.launcher.daemon.bootstrap.GradleDaemon 8.3

Unhandled error in Gradle post-action - job will continue: Error: EBUSY: resource busy or locked, unlink 'C:\Users\runneradmin\.gradle\caches\8.3\generated-gradle-jars\gradle-kotlin-dsl-extensions-8.3.jar'

Failed to delete C:\Users\runneradmin\.gradle\caches\8.3\generated-gradle-jars\gradle-kotlin-dsl-extensions-8.3.jar, which will impact caching. It is likely locked by another process. Output of 'jps -ml': 6368 sun.tools.jps.Jps -lm 3924 org.gradle.launcher.daemon.bootstrap.GradleDaemon 8.3 748 sun.tools.jps.Jps -lm

Unhandled error in Gradle post-action - job will continue: Error: EBUSY: resource busy or locked, unlink 'C:\Users\runneradmin\.gradle\caches\8.3\generated-gradle-jars\gradle-api-8.3.jar'

Failed to delete C:\Users\runneradmin\.gradle\caches\8.3\generated-gradle-jars\gradle-api-8.3.jar, which will impact caching. It is likely locked by another process. Output of 'jps -ml': 6368 sun.tools.jps.Jps -lm 3924 org.gradle.launcher.daemon.bootstrap.GradleDaemon 8.3 748 sun.tools.jps.Jps -lm

Failed to save cache entry with path 'C:\Users\runneradmin\.gradle\caches,C:\Users\runneradmin\.gradle\notifications,C:\Users\runneradmin\.gradle\.gradle-build-action' and key: v8-gradle|Windows|dafny nightly-testDotNet[a17ef54e30a2706477b144c6a5b8220a]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: "C:\Program failed with error: The process 'C:\Program Files\Git\usr\bin\tar.exe' failed with exit code 2

Failed to save cache entry with path 'C:\Users\runneradmin\.gradle\caches\jars-*\*' and key: instrumented-jars-964fa38104462d3e543d0d64e1102b67: Error: "C:\Program failed with error: The process 'C:\Program Files\Git\usr\bin\tar.exe' failed with exit code 2

Failed to restore v8-gradle|Windows|dafny nightly-testDotNet[a17ef54e30a2706477b144c6a5b8220a]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to restore v8-gradle|macOS|dafny nightly-verification[545a550a27e57d36908fc3be86e57dbd]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to restore v8-gradle|macOS|dafny nightly-verification[e5cceaebdaf758faf8cf9ba232405382]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to restore v8-gradle|macOS|dafny nightly-verification[b2c9c9803f8804875da09df8576b6d1b]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to restore v8-gradle|macOS|dafny nightly-verification[7cba8ad3265adf31fb0a602ac71ef80e]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to restore v8-gradle|Linux|dafny nightly-testRust[795159b82cac2846154e488c4edbad8e]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to restore v8-gradle|Linux|dafny nightly-testRust[6c680655a126b152b57aacb5eb872519]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to restore v8-gradle|macOS|dafny nightly-verification[69fda0abad2f052e09e4586816baf717]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to restore v8-gradle|macOS|dafny nightly-testJava[ef3257e4e5b42193600dc2e92ccca30e]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to restore v8-gradle|macOS|dafny nightly-testJava[79e2784693b2fc2d9c8ffa85a85b6175]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to restore v8-gradle|macOS|dafny nightly-testJava[dcffed718fb1e9dc2cf358dcf37e2c94]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to restore v8-gradle|macOS|dafny nightly-testJava[8d322c5d081dad8da1230e33312cf260]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to restore v8-gradle|macOS|dafny nightly-testRust[7cba8ad3265adf31fb0a602ac71ef80e]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to restore v8-gradle|macOS|dafny nightly-testRust[071027feb64b35675e0730c602830e0e]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!

Treating docker as a formula. For the cask, use homebrew/cask/docker or specify the `--cask` flag. To silence this message, use the `--formula` flag.