Update sbt, scripted-plugin to 1.10.7 #1459
scala-stewardbuild.yml
on: pull_request
checksecret
0s
Matrix: test-site
Matrix: build-js
Matrix: build-jvm
Annotations
10 errors and 35 warnings
|
build-jvm (11, 3)
Error: Unable to locate executable file: sbt. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
|
|
build-jvm (11, 2.12)
Error: Unable to locate executable file: sbt. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
|
|
build-jvm (11, 2.13)
Error: Unable to locate executable file: sbt. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
|
|
build-jvm (17, 2.12)
Error: Unable to locate executable file: sbt. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
|
|
build-jvm (17, 2.13)
Error: Unable to locate executable file: sbt. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
|
|
build-jvm (17, 3)
Error: Unable to locate executable file: sbt. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
|
|
build-jvm (22, 2.12)
Error: Unable to locate executable file: sbt. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
|
|
build-jvm (22, 3)
Error: Unable to locate executable file: sbt. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
|
|
build-jvm (22, 2.13)
Error: Unable to locate executable file: sbt. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.
|
|
all-good
Process completed with exit code 1.
|
|
checksecret
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
test-site (22, 2.13)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-js (22, 2.12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-js (17, 2.13)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-js (17, 2.12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-js (22, 2.13)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-js (17, 3)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-js (11, 2.12)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-js (11, 2.13)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-js (11, 3)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
build-js (22, 3)
Failed to restore: Cache service responded with 429
|
|
build-js (22, 3)
Failed to restore: Cache service responded with 429
|
|
build-js (22, 3)
Failed to restore: Cache service responded with 429
|
|
build-jvm (11, 3)
Failed to restore: Cache service responded with 429
|
|
build-jvm (11, 3)
Failed to restore: Cache service responded with 429
|
|
build-jvm (11, 3)
Failed to restore: Cache service responded with 429
|
|
build-jvm (11, 2.12)
Failed to restore: Cache service responded with 429
|
|
build-jvm (11, 2.12)
Failed to restore: Cache service responded with 429
|
|
build-jvm (11, 2.12)
Failed to restore: Cache service responded with 429
|
|
build-jvm (11, 2.13)
Failed to restore: Cache service responded with 429
|
|
build-jvm (11, 2.13)
Failed to restore: Cache service responded with 429
|
|
build-jvm (11, 2.13)
Failed to restore: Cache service responded with 429
|
|
build-jvm (17, 2.12)
Failed to restore: Cache service responded with 429
|
|
build-jvm (17, 2.12)
Failed to restore: Cache service responded with 429
|
|
build-jvm (17, 2.12)
Failed to restore: Cache service responded with 429
|
|
build-jvm (17, 2.13)
Failed to restore: Cache service responded with 429
|
|
build-jvm (17, 2.13)
Failed to restore: Cache service responded with 429
|
|
build-jvm (17, 2.13)
Failed to restore: Cache service responded with 429
|
|
build-jvm (17, 3)
Failed to restore: Cache service responded with 429
|
|
build-jvm (17, 3)
Failed to restore: Cache service responded with 429
|
|
build-jvm (17, 3)
Failed to restore: Cache service responded with 429
|
|
build-jvm (22, 2.12)
Failed to restore: Cache service responded with 429
|
|
build-jvm (22, 3)
Failed to restore: Cache service responded with 429
|
|
build-jvm (22, 3)
Failed to restore: Cache service responded with 429
|
|
build-jvm (22, 2.13)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|