Bump quarto-dev/quarto-actions from 2.1.6 to 2.1.7 #526
Triggered via pull request
January 1, 2025 00:51
Status
Failure
Total duration
1h 30m 42s
Artifacts
–
CI.yml
on: pull_request
Matrix: test
format
52s
finalize
0s
Annotations
4 errors, 7 warnings, and 3 notices
test (1.7, macos-13)
No such keg: /usr/local/Cellar/[email protected]
|
test (1.11, macos-13)
No such keg: /usr/local/Cellar/[email protected]
|
test (1.6, ubuntu-latest)
The job running on runner GitHub Actions 64 has exceeded the maximum execution time of 90 minutes.
|
finalize
Process completed with exit code 1.
|
format
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
test (1.7, macos-13)
pkgconf 2.3.0_1 is already installed and up-to-date.
To reinstall 2.3.0_1, run:
brew reinstall pkgconf
|
test (1.7, macos-13)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated
dependents or dependents with broken linkage!
|
test (1.11, ubuntu-latest)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
test (1.11, macos-13)
pkgconf 2.3.0_1 is already installed and up-to-date.
To reinstall 2.3.0_1, run:
brew reinstall pkgconf
|
test (1.11, macos-13)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated
dependents or dependents with broken linkage!
|
finalize
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
[julia-buildpkg] Caching of the julia depot was not detected
Consider using `julia-actions/cache` to speed up runs https://github.com/julia-actions/cache To ignore, set input `ignore-no-cache: true`
|
[julia-buildpkg] Caching of the julia depot was not detected
Consider using `julia-actions/cache` to speed up runs https://github.com/julia-actions/cache To ignore, set input `ignore-no-cache: true`
|
test (1.6, ubuntu-latest)
[setup-julia] If you are testing 1.6 as a Long Term Support (lts) version, consider using the new "lts" version specifier instead of "1.6" explicitly, which will automatically resolve the current lts.
|