Skip to content

fix(canary): give the dry-run a timeout a real deploy can finish inside #122

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sgardoll merged 1 commit into from
Oct 4, 2026
Merged

fix(canary): give the dry-run a timeout a real deploy can finish inside #122

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion scripts/canary-deploy.mjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,11 @@ async function main() {
"",
);
const projectId = process.env.CANARY_PROJECT_ID || "automated-test-miedro";
const timeoutMs = Number(process.env.CANARY_TIMEOUT_MS || 60000);
// A real deploy takes 103-215s (measured on the production runner), and this
// canary drives the same path, so a 60s bound made every scheduled run fail
// with "timed out" - a daily false alarm that would mask a real one. Sized
// above the slowest observed deploy and below Cloud Run's 900s request cap.
const timeoutMs = Number(process.env.CANARY_TIMEOUT_MS || 300000);

const payload = {
apiKey,
Expand Down
Loading