Run tests #169
Triggered via schedule
February 16, 2025 03:30
Status
Failure
Total duration
1d 4h 25m 8s
Artifacts
–
Annotations
7 errors, 13 warnings, and 2 notices
doctest (nightly, ubuntu-latest)
Process completed with exit code 1.
|
test (nightly, book, ubuntu-latest)
Process completed with exit code 1.
|
test (nightly, long, ubuntu-latest)
Process completed with exit code 1.
|
test (nightly, short, ubuntu-latest)
Process completed with exit code 1.
|
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, long, 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.
|
doctest (nightly, ubuntu-latest)
Cache not found for keys: julia-cache;workflow=Run tests;julia=nightly;arch=X64;os=Linux;run_id=13351340158;run_attempt=1, julia-cache;workflow=Run tests;julia=nightly;arch=X64;os=Linux;
|
doctest (1.10, ubuntu-latest, depwarn=error)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
test (nightly, book, ubuntu-latest)
Cache not found for keys: julia-cache;workflow=Run tests;julia=nightly;arch=X64;os=Linux;run_id=13351340158;run_attempt=1, julia-cache;workflow=Run tests;julia=nightly;arch=X64;os=Linux;
|
test (nightly, long, ubuntu-latest)
Cache not found for keys: julia-cache;workflow=Run tests;julia=nightly;arch=X64;os=Linux;run_id=13351340158;run_attempt=1, julia-cache;workflow=Run tests;julia=nightly;arch=X64;os=Linux;
|
test (nightly, short, ubuntu-latest)
Cache not found for keys: julia-cache;workflow=Run tests;julia=nightly;arch=X64;os=Linux;run_id=13351340158;run_attempt=1, julia-cache;workflow=Run tests;julia=nightly;arch=X64;os=Linux;
|
test (1.10, long, ubuntu-latest, depwarn=error)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
test (1.10, long, ubuntu-latest)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
test (1.11-nightly, long, ubuntu-latest)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
test (1.10, book, ubuntu-latest)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
test (1.10, short, ubuntu-latest)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
test (1.10, short, ubuntu-latest, depwarn=error)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
test (1.11-nightly, short, ubuntu-latest)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
test (1.6, short, ubuntu-latest)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
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.
|