ci: don't fail the job on Azure launch errors - #42
Merged
Conversation
The Azure compute environment's Batch pool is currently stale, which was failing every PR's CI regardless of the actual change. Mark the azure_run step continue-on-error so AWS/GCP launches and the overall job aren't blocked by it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
🚀 Pipelines launched
|
edmundmiller
approved these changes
Aug 18, 2026
Add an explicit status row so a non-blocking Azure failure is visible instead of showing blank fields. Also fixes a copy-paste bug where the Azure Workflow URL row read from steps.gcp_run instead of azure_run. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Member
Author
|
Sorry @adamrtalbot - can bring back later if you want! |
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
tower-pool-...does not exist), which was failing CI on every PR regardless of the actual change.azure_runstepcontinue-on-error: trueso AWS/GCP launches and the overall job status aren't blocked by it.Test plan