Skip to content

Conversation

@Samze
Copy link
Contributor

@Samze Samze commented Mar 13, 2025

This command had different behaviour depending on if the deployment would complete in time for the CANCEL command to be issued.

Instead we use a canary, which requires a manual continue, so the deployment is always in a cancellable state.

We also then make sure through the API that this command calls cancel when the deployment fails.

Copy link
Member

@gururajsh gururajsh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

This command had different behaviour depending on if the deployment
would complete in time for the CANCEL command to be issued.

Instead we use a canary, which requires a manual continue, so the
deployment is always in a cancellable state.

We also then make sure through the API that this command calls cancel
when the deployment fails.
@a-b a-b force-pushed the v8_fix_restage_flake branch from f179bd2 to cc54a4b Compare March 14, 2025 15:44
@Samze Samze merged commit 28400e3 into v8 Mar 14, 2025
15 checks passed
@Samze Samze deleted the v8_fix_restage_flake branch March 14, 2025 16:23
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.

3 participants