Initial expressify test #639
Triggered via pull request
January 29, 2025 20:03
SoongNoonien
Status
Cancelled
Total duration
13m 57s
Artifacts
–
CI.yml
on: pull_request
Documentation
13m 50s
Matrix: test
Annotations
12 errors and 3 notices
|
test (1.11, stable, ubuntu-latest)
Process completed with exit code 1.
|
|
test (nightly, stable, ubuntu-latest)
Process completed with exit code 1.
|
|
test (1.11, 1.1, ubuntu-latest)
Process completed with exit code 1.
|
|
test (1.11, devel, ubuntu-latest)
Process completed with exit code 1.
|
|
test (1.6, 1.1, ubuntu-latest)
Process completed with exit code 1.
|
|
test (1.6, stable, ubuntu-latest)
Process completed with exit code 1.
|
|
test (nightly, devel, ubuntu-latest)
Process completed with exit code 1.
|
|
test (1.10, stable, ubuntu-latest)
Process completed with exit code 1.
|
|
test (1.6, devel, ubuntu-latest)
Process completed with exit code 1.
|
|
test (1.10, devel, ubuntu-latest)
Process completed with exit code 1.
|
|
test (1.10, 1.1, ubuntu-latest)
Process completed with exit code 1.
|
|
Documentation
Canceling since a higher priority waiting request for 'Run tests-refs/pull/248/merge-true' exists
|
|
test (1.6, 1.1, 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.
|
|
test (1.6, stable, 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.
|
|
test (1.6, devel, 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.
|