Skip to content

Fix timeseries dataset integration into workflows (#2) #9

Fix timeseries dataset integration into workflows (#2)

Fix timeseries dataset integration into workflows (#2) #9

Triggered via push June 10, 2025 13:44
Status Failure
Total duration 2m 34s
Artifacts

main.yml

on: push
Check coding standards
54s
Check coding standards
Matrix: Run tests
Fit to window
Zoom out
Zoom in

Annotations

11 errors and 6 warnings
Run tests (Ubuntu, 3.12)
ENOENT: no such file or directory, open 'test-report.xml'
Run tests (Ubuntu, 3.12)
Process completed with exit code 1.
Run tests (Ubuntu, 3.10)
ENOENT: no such file or directory, open 'test-report.xml'
Run tests (Ubuntu, 3.10)
The operation was canceled.
Run tests (Ubuntu, 3.10)
The strategy configuration was canceled because "tests.Ubuntu_3_12" failed
Run tests (Ubuntu, 3.13)
ENOENT: no such file or directory, open 'test-report.xml'
Run tests (Ubuntu, 3.13)
The operation was canceled.
Run tests (Ubuntu, 3.13)
The strategy configuration was canceled because "tests.Ubuntu_3_12" failed
Run tests (Ubuntu, 3.11)
ENOENT: no such file or directory, open 'test-report.xml'
Run tests (Ubuntu, 3.11)
The operation was canceled.
Run tests (Ubuntu, 3.11)
The strategy configuration was canceled because "tests.Ubuntu_3_12" failed
Check coding standards
Failed to save: reserveCache failed: Cache service responded with 503
Check coding standards
Failed to restore: getCacheEntry failed: Cache service responded with 503
Run tests (Ubuntu, 3.12)
Failed to restore: getCacheEntry failed: Cache service responded with 503
Run tests (Ubuntu, 3.10)
Failed to restore: getCacheEntry failed: Cache service responded with 503
Run tests (Ubuntu, 3.13)
Failed to restore: getCacheEntry failed: Cache service responded with 503
Run tests (Ubuntu, 3.11)
Failed to restore: getCacheEntry failed: Cache service responded with 503