Run tests #41
Triggered via schedule
October 31, 2024 03:32
emikelsons
Status
Failure
Total duration
1d 12h 2m 58s
Artifacts
–
Annotations
4 errors, 3 warnings, and 2 notices
|
test (1.10, book, ubuntu-latest)
The job running on runner GitHub Actions 5 has exceeded the maximum execution time of 150 minutes.
|
|
doctest (1.10, macOS, RPTU)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
|
test (1.10, short, macOS, RPTU)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
|
test (1.10, long, macOS, RPTU)
This request was automatically failed because there were no enabled runners online to process the request for more than 1 days.
|
|
doctest (1.10, ubuntu-latest)
Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
|
|
test (1.10, long, ubuntu-latest)
Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
|
|
test (1.10, short, ubuntu-latest)
Codecov: Failed to properly create commit: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1
|
|
test (1.6, long, 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, short, 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.
|