Gradle build failed: see console output for details

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

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

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

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

Gradle build failed: see console output for details

The operation was canceled.

Gradle build failed: see console output for details

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

Gradle build failed: see console output for details

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-java.testJava.TestVectors_11_ubuntu-22_" failed

The operation was canceled.

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

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

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 hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.

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

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|Linux|dafny nightly-testDotNet[7206fa0e0cedb6913d76412c6501ba2d]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

Failed to delete C:\Users\runneradmin\.gradle\caches\jars-9\66dcb0dc22db6e56ce3edddaaab14cb4, which will impact caching. It is likely locked by another process. Output of 'jps -ml': 4592 sun.tools.jps.Jps -lm 5552 sun.tools.jps.Jps -lm 5776 org.gradle.launcher.daemon.bootstrap.GradleDaemon 8.3 6048 sun.tools.jps.Jps -lm 1608 sun.tools.jps.Jps -lm 4328 sun.tools.jps.Jps -lm 536 sun.tools.jps.Jps -lm 968 sun.tools.jps.Jps -lm 3148 sun.tools.jps.Jps -lm 4716 -- process information unavailable 6780 -- process information unavailable

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

Failed to delete C:\Users\runneradmin\.gradle\caches\jars-9\c8bf2e959876d19fd4afe508910217d5, which will impact caching. It is likely locked by another process. Output of 'jps -ml': 4592 sun.tools.jps.Jps -lm 5552 sun.tools.jps.Jps -lm 5776 org.gradle.launcher.daemon.bootstrap.GradleDaemon 8.3 6048 sun.tools.jps.Jps -lm 1608 sun.tools.jps.Jps -lm 4328 sun.tools.jps.Jps -lm 536 sun.tools.jps.Jps -lm 968 sun.tools.jps.Jps -lm 3148 sun.tools.jps.Jps -lm 4716 sun.tools.jps.Jps -lm 6780 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\jars-9\jars-9.lock'

Failed to delete C:\Users\runneradmin\.gradle\caches\jars-9\jars-9.lock, which will impact caching. It is likely locked by another process. Output of 'jps -ml': 4592 sun.tools.jps.Jps -lm 5552 sun.tools.jps.Jps -lm 5776 org.gradle.launcher.daemon.bootstrap.GradleDaemon 8.3 6048 sun.tools.jps.Jps -lm 1608 sun.tools.jps.Jps -lm 4328 -- process information unavailable 536 sun.tools.jps.Jps -lm 968 sun.tools.jps.Jps -lm 3148 sun.tools.jps.Jps -lm 4716 -- process information unavailable 6780 -- process information unavailable

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

Failed to delete C:\Users\runneradmin\.gradle\caches\jars-9\da0250623251edc138c21b0b81c96707, which will impact caching. It is likely locked by another process. Output of 'jps -ml': 5552 sun.tools.jps.Jps -lm 5776 org.gradle.launcher.daemon.bootstrap.GradleDaemon 8.3 6048 sun.tools.jps.Jps -lm 1608 -- process information unavailable 4328 -- process information unavailable 536 sun.tools.jps.Jps -lm 968 sun.tools.jps.Jps -lm 3148 sun.tools.jps.Jps -lm 4716 -- process information unavailable 6780 -- process information unavailable

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

Failed to delete C:\Users\runneradmin\.gradle\caches\jars-9\0b5d216730858c641c3bc5cb4b1ca303, which will impact caching. It is likely locked by another process. Output of 'jps -ml': 4592 sun.tools.jps.Jps -lm 5552 sun.tools.jps.Jps -lm 5776 org.gradle.launcher.daemon.bootstrap.GradleDaemon 8.3 1608 sun.tools.jps.Jps -lm 4328 sun.tools.jps.Jps -lm 536 sun.tools.jps.Jps -lm 4716 sun.tools.jps.Jps -lm 6780 sun.tools.jps.Jps -lm

Failed to save cache entry with path 'C:\Users\runneradmin\.gradle\caches\jars-*\*' and key: instrumented-jars-87baa814d930272a6ca80ed70c564eb0: 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

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!

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[545a550a27e57d36908fc3be86e57dbd]-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[dcffed718fb1e9dc2cf358dcf37e2c94]-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[8d322c5d081dad8da1230e33312cf260]-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|macOS|dafny nightly-verification[e5cceaebdaf758faf8cf9ba232405382]-ccf61d6a9c49385f1cccde0cda9c0609ba050455: Error: Cache service responded with 422

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