Simple parallelization framework #18455
Triggered via pull request
January 28, 2025 18:47
antonydellavecchia
Status
Failure
Total duration
2h 35m 48s
Artifacts
–
Annotations
19 errors and 2 notices
|
test (1.11, short, Linux)
Process completed with exit code 1.
|
|
test (1.10, short, macOS, RPTU)
Process completed with exit code 1.
|
|
test (1.6, short, Linux)
Process completed with exit code 1.
|
|
test (1.10, long, macOS, RPTU)
Process completed with exit code 1.
|
|
test (1.6, long, 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, short, Linux)
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.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.
|
|
doctest (1.10, Linux, RPTU, normal-memory, depwarn=error)
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 (nightly, Linux, RPTU, normal-memory)
Process completed with exit code 1.
|
|
test (nightly, long, Linux)
Process completed with exit code 1.
|
|
test (nightly, book, Linux, RPTU, normal-memory)
Process completed with exit code 1.
|
|
test (1.10, book, Linux, RPTU, normal-memory)
The job running on runner RPTU-Linux-08 has exceeded the maximum execution time of 150 minutes.
|
|
test (nightly, short, Linux)
The job running on runner RPTU-Linux-13 has exceeded the maximum execution time of 150 minutes.
|
|
test (1.6, short, 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.
|
|
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.
|