Skip to content

Improve inferrability (#308) #297

Improve inferrability (#308)

Improve inferrability (#308) #297

Triggered via push October 12, 2024 19:36
Status Success
Total duration 17m 28s
Artifacts

CI.yml

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

Annotations

2 warnings and 13 notices
Documentation
The following actions uses node12 which is deprecated and will be forced to run on node16: julia-actions/julia-docdeploy@releases/v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Documentation
The following actions use a deprecated Node.js version and will be forced to run on node20: julia-actions/julia-docdeploy@releases/v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Julia 1.6 - ubuntu-latest - x64 - provider fftw - 2 thread(s)
[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 1.6 - ubuntu-latest - x64 - provider fftw - 1 thread(s)
[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 1.6 - ubuntu-latest - x86 - provider fftw - 2 thread(s)
[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 1.6 - ubuntu-latest - x86 - provider fftw - 1 thread(s)
[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 1.6 - macOS-13 - x64 - provider fftw - 2 thread(s)
[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 1.6 - macOS-13 - x64 - provider fftw - 1 thread(s)
[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 1.6 - ubuntu-latest - x64 - provider mkl - 1 thread(s)
[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 1.6 - windows-latest - x64 - provider fftw - 1 thread(s)
[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 1.6 - windows-latest - x64 - provider fftw - 2 thread(s)
[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 1.6 - windows-latest - x86 - provider fftw - 2 thread(s)
[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 1.6 - windows-latest - x86 - provider mkl - 1 thread(s)
[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 1.6 - windows-latest - x86 - provider fftw - 1 thread(s)
[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 1.6 - windows-latest - x64 - provider mkl - 1 thread(s)
[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.