Skip to content

Serialization Refactor #18579

Serialization Refactor

Serialization Refactor #18579

Triggered via pull request February 5, 2025 10:02
Status Failure
Total duration 39m 11s
Artifacts

CI.yml

on: pull_request
extra-long-test
0s
extra-long-test
Matrix: doctest
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

19 errors and 1 notice
doctest (nightly, Linux, RPTU, normal-memory)
Process completed with exit code 1.
test (nightly, book, Linux, RPTU, normal-memory)
Process completed with exit code 1.
test (nightly, long, Linux)
Process completed with exit code 1.
test (1.11, short, Linux)
Process completed with exit code 1.
test (1.10, short, macOS, RPTU)
Process completed with exit code 1.
test (nightly, short, Linux)
Process completed with exit code 1.
test (1.10, short, Linux)
Process completed with exit code 1.
test (1.10, short, Linux, RPTU, high-memory, depwarn=error)
Process completed with exit code 1.
test (1.10, long, macOS, RPTU)
Process completed with exit code 1.
doctest (1.10, macOS, RPTU)
Process completed with exit code 1.
test (1.11, long, Linux)
Process completed with exit code 1.
test (1.6, short, Linux)
The self-hosted runner: RPTU-Linux-11 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
test (1.10, long, Linux)
Process completed with exit code 1.
test (1.10, long, Linux, RPTU, normal-memory, depwarn=error)
Process completed with exit code 1.
test (1.6, long, Linux)
Process completed with exit code 1.
doctest (1.11, Linux, RPTU, normal-memory)
Process completed with exit code 1.
doctest (1.10, Linux, RPTU, normal-memory)
Process completed with exit code 1.
doctest (1.10, Linux, RPTU, normal-memory, depwarn=error)
Process completed with exit code 1.
test (1.10, book, Linux, RPTU, normal-memory)
Process completed with exit code 1.
test (1.6, long, Linux)
[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.