Skip to content
Tests

Enable coverage tracking #131

Sign in to view logs

Enable coverage tracking

Enable coverage tracking #131

Triggered via pull request July 3, 2025 14:33
@MatthiasValvekensMatthiasValvekens
synchronize #210
MatthiasValvekens:maintenance/coverage
Status Success
Total duration 2m 12s
Artifacts –

tests.yml

on: pull_request
Matrix: run
Fit to window
Zoom out
Zoom in

Annotations

30 warnings
run (macos-latest, 3.11)
Failed to save: reserveCache failed: Cache service responded with 503
run (macos-latest, 3.11)
Failed to restore: getCacheEntry failed: Cache service responded with 503
run (macos-latest, 3.12)
Failed to save: reserveCache failed: Cache service responded with 503
run (macos-latest, 3.12)
Failed to restore: getCacheEntry failed: Cache service responded with 503
run (macos-latest, 3.13)
Failed to save: reserveCache failed: Cache service responded with 503
run (macos-latest, 3.13)
Failed to restore: getCacheEntry failed: Cache service responded with 503
run (ubuntu-latest, 3.9)
Failed to save: reserveCache failed: Cache service responded with 503
run (ubuntu-latest, 3.9)
Failed to restore: getCacheEntry failed: Cache service responded with 503
run (macos-latest, 3.10)
Failed to save: reserveCache failed: Cache service responded with 503
run (macos-latest, 3.10)
Failed to restore: getCacheEntry failed: Cache service responded with 503
run (ubuntu-latest, 3.13)
Failed to save: reserveCache failed: Cache service responded with 503
run (ubuntu-latest, 3.13)
Failed to restore: getCacheEntry failed: Cache service responded with 503
run (macos-latest, 3.9)
Failed to save: reserveCache failed: Cache service responded with 503
run (macos-latest, 3.9)
Failed to restore: getCacheEntry failed: Cache service responded with 503
run (ubuntu-latest, 3.11)
Failed to save: reserveCache failed: Cache service responded with 503
run (ubuntu-latest, 3.11)
Failed to restore: getCacheEntry failed: Cache service responded with 503
run (windows-latest, 3.10)
Failed to save: reserveCache failed: Cache service responded with 503
run (windows-latest, 3.10)
Failed to restore: getCacheEntry failed: Cache service responded with 503
run (windows-latest, 3.12)
Failed to save: reserveCache failed: Cache service responded with 503
run (windows-latest, 3.12)
Failed to restore: getCacheEntry failed: Cache service responded with 503
run (windows-latest, 3.9)
Failed to save: reserveCache failed: Cache service responded with 503
run (windows-latest, 3.9)
Failed to restore: getCacheEntry failed: Cache service responded with 503
run (windows-latest, 3.13)
Failed to save: reserveCache failed: Cache service responded with 503
run (windows-latest, 3.13)
Failed to restore: getCacheEntry failed: Cache service responded with 503
run (windows-latest, 3.11)
Failed to save: reserveCache failed: Cache service responded with 503
run (windows-latest, 3.11)
Failed to restore: getCacheEntry failed: Cache service responded with 503
run (ubuntu-latest, 3.12)
Failed to save: reserveCache failed: Cache service responded with 503
run (ubuntu-latest, 3.12)
Failed to restore: getCacheEntry failed: Cache service responded with 503
run (ubuntu-latest, 3.10)
Failed to save: reserveCache failed: Cache service responded with 503
run (ubuntu-latest, 3.10)
Failed to restore: getCacheEntry failed: Cache service responded with 503