Skip to content
CI

avoid private access to loaded_precompile #516

Sign in to view logs

avoid private access to loaded_precompile

avoid private access to loaded_precompile #516

Triggered via pull request October 5, 2024 13:47
@vtjnashvtjnash
opened #856
jn/maybe_loaded_precompile
Status Failure
Total duration 28m 50s
Artifacts –

ci.yml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 6 notices
Install & test Julia nightly - ubuntu-latest - x64 - pull_request
Process completed with exit code 1.
Install & test Julia pre - ubuntu-latest - x64 - pull_request
Process completed with exit code 1.
Install & test Julia pre - windows-latest - x64 - pull_request
Process completed with exit code 1.
Install & test Julia pre - macOS-latest - x64 - pull_request
Process completed with exit code 1.
Install & test Julia 1.6 - ubuntu-latest - x64 - pull_request
[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.
[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`
Install & test Julia 1.6 - windows-latest - x64 - pull_request
[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.
[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`
Install & test Julia 1.6 - macOS-latest - x64 - pull_request
[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.