Skip to content
Run tests

Run tests #5786

Sign in to view logs

Run tests

Run tests #5786

Triggered via schedule November 16, 2024 03:33
@thofmathofma
⁠ 0d6625a
master
Status Success
Total duration 1h 29m 53s
Artifacts –

CI.yml

on: schedule
Documentation
10m 30s
Documentation
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

10 warnings and 2 notices
Documentation: ../../../.julia/packages/DocumenterVitepress/8qgu7/src/vitepress_config.jl#L111
DocumenterVitepress: No logo.png file found in `docs/src/assets`. Skipping logo replacement.
Documentation: ../../../.julia/packages/DocumenterVitepress/8qgu7/src/vitepress_config.jl#L122
DocumenterVitepress: No favicon.ico file found in `docs/src/assets`. Skipping favicon replacement.
Documentation: ../../../.julia/packages/Documenter/Bs999/src/deploydocs.jl#L552
removing `stable` and linking `stable` to `v0.34.7`.
Documentation: ../../../.julia/packages/Documenter/Bs999/src/deploydocs.jl#L552
removing `v0.34` and linking `v0.34` to `v0.34.7`.
Documentation: ../../../.julia/packages/Documenter/Bs999/src/deploydocs.jl#L552
removing `v0.33` and linking `v0.33` to `v0.33.8`.
Documentation: ../../../.julia/packages/Documenter/Bs999/src/deploydocs.jl#L552
removing `v0.32` and linking `v0.32` to `v0.32.3`.
Documentation: ../../../.julia/packages/Documenter/Bs999/src/deploydocs.jl#L552
removing `v0.31` and linking `v0.31` to `v0.31.5`.
Documentation: ../../../.julia/packages/Documenter/Bs999/src/deploydocs.jl#L552
removing `v0.30` and linking `v0.30` to `v0.30.12`.
Documentation: ../../../.julia/packages/Documenter/Bs999/src/deploydocs.jl#L552
removing `v0.29` and linking `v0.29` to `v0.29.1`.
Documentation: ../../../.julia/packages/Documenter/Bs999/src/deploydocs.jl#L552
removing `v0.28` and linking `v0.28` to `v0.28.0`.
[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.