Skip to content
Tests

process: handle possible fio.read errors #1084

Sign in to view logs

process: handle possible fio.read errors

process: handle possible fio.read errors #1084

Triggered via push October 8, 2025 14:02
@olegrokolegrok
pushed 65bcb18
526-fio-read-error
Status Success
Total duration 14m 35s
Artifacts –

test.yml

on: push
Matrix: test
packpack
1m 33s
packpack
Matrix: promtool
Fit to window
Zoom out
Zoom in

Annotations

36 warnings
test (2.11)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0GW/maAAAAACRojHgrD5pRIJPe1Q20ng7UEhMMzBFREdFMDQyMQBFZGdl
test (2.11)
Failed to restore: Cache service responded with 400
test (3.0)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Em/maAAAAAArINmM9xcZQprlfCk8tY5qQ0hJMzBFREdFMDQwNwBFZGdl
test (3.0)
Failed to restore: Cache service responded with 400
test (3.1)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0F2/maAAAAAD25CqSFPvES6oYBr4F2wzNRE0yRURHRTA3MDkARWRnZQ==
test (3.1)
Failed to restore: Cache service responded with 400
test (3.2)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0F2/maAAAAAC8mHfCo7mDSpMmJgNq5TwOUEFPRURHRTA1MTMARWRnZQ==
test (3.2)
Failed to restore: Cache service responded with 400
test (2.11, 2.9.0)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Fm/maAAAAAC29ChebG9STLpDXhJC2EbOUEhMMzBFREdFMDIxMgBFZGdl
test (2.11, 2.9.0)
Failed to restore: Cache service responded with 400
test (2.11, 2.10.0)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Gm/maAAAAAAkhRdMFoyCQbAfHETQY130Q0hJMzBFREdFMDQxNwBFZGdl
test (2.11, 2.10.0)
Failed to restore: Cache service responded with 400
test (3.4.1)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ZW/maAAAAADaPCu71pubTL5IlRRGXhMYRE0yRURHRTAxMjAARWRnZQ==
test (3.4.1)
Failed to restore: Cache service responded with 400
test (3.3)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0bm/maAAAAADP37gWSIs0TLtamewhuSnTUEhMMzBFREdFMDExMgBFZGdl
test (3.3)
Failed to restore: Cache service responded with 400
test (3.5)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0hm/maAAAAAA/8FShXaiKTKsjSSmysygAQ0hJMzBFREdFMDMxNABFZGdl
test (3.5)
Failed to restore: Cache service responded with 400
test (2.11, 2.7.9)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0cG/maAAAAADg4gRQCLsrQoFJb/ewbA2gRE0yRURHRTA1MjIARWRnZQ==
test (2.11, 2.7.9)
Failed to restore: Cache service responded with 400
test (2.11, 2.16.3)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0k2/maAAAAABcvjdDkCQcS5rmVZfEARBhQ0hJMzBFREdFMDMxOABFZGdl
test (2.11, 2.16.3)
Failed to restore: Cache service responded with 400
test (2.11, 2.11.0)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0h2/maAAAAAC4h757BUA8RYhWK14hoGH/UEhMMzBFREdFMDExMwBFZGdl
test (2.11, 2.11.0)
Failed to restore: Cache service responded with 400
test (2.11, 2.8.6)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0jW/maAAAAADL7u+KjH/aRaSwP3gur1cXQ0hJMzBFREdFMDMxOABFZGdl
test (2.11, 2.8.6)
Failed to restore: Cache service responded with 400
test (2.11, 2.13.0)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0kG/maAAAAADq7O4YAi0DQJNd5iPPmmtlQ0hJMzBFREdFMDIxMwBFZGdl
test (2.11, 2.13.0)
Failed to restore: Cache service responded with 400
test (2.11, 2.12.4)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0zW/maAAAAAAbEXQGJABoTr7Gh2Iyi4PUUEhMMzBFREdFMDEyMgBFZGdl
test (2.11, 2.12.4)
Failed to restore: Cache service responded with 400
promtool (3.1)
Restore cache failed: Dependencies file is not found in /home/runner/work/metrics/metrics. Supported file pattern: go.sum
promtool (3.1)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0e3HmaAAAAACzKZsaHOP3TLfjV+6A/du/UEhMMzBFREdFMDEwOQBFZGdl
promtool (3.1)
Failed to restore: Cache service responded with 400
promtool (2.11, 2.10.0)
Restore cache failed: Dependencies file is not found in /home/runner/work/metrics/metrics. Supported file pattern: go.sum
promtool (2.11, 2.10.0)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0s3HmaAAAAAAhvcFP0indQJTW3X6Kz6RVREVOMzAxMDAwMTAzMDM5AEVkZ2U=
promtool (2.11, 2.10.0)
Failed to restore: Cache service responded with 400