Skip to content

🐛 fix(ci): retry qlty on timeout and increase limit to 8 minutes#131

Closed
s-b-e-n-s-o-n wants to merge 1 commit intomainfrom
release/v1.4.0-rc.11
Closed

🐛 fix(ci): retry qlty on timeout and increase limit to 8 minutes#131
s-b-e-n-s-o-n wants to merge 1 commit intomainfrom
release/v1.4.0-rc.11

Conversation

@s-b-e-n-s-o-n
Copy link
Contributor

Summary

  • Change retry_on from error to any so qlty timeouts actually trigger retries
  • Increase timeout from 5 to 8 minutes to accommodate qlty's variable CI runtime

Context

The Lint job failed on the main push after merging PR #129qlty check hit the 5-minute timeout but retry_on: error only retries on non-zero exit codes, not timeouts. The job failed on attempt 1 without retrying.

retry_on was set to "error" which only retries on non-zero exit codes,
not on timeouts. Changed to "any" so the 5-minute timeout actually
triggers a retry. Also bumped timeout from 5 to 8 minutes since qlty
regularly takes longer in CI.
@vercel
Copy link

vercel bot commented Mar 9, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
drydock-website Ready Ready Preview, Comment Mar 9, 2026 10:15pm

@codecov
Copy link

codecov bot commented Mar 9, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@s-b-e-n-s-o-n
Copy link
Contributor Author

Folding into the next RC with compose Docker Engine API fixes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant