Skip to content

ci(subsystembenchmarks): harden stale VM cleanup - #983

Merged
zhixiangli merged 2 commits into
fsspec:mainfrom
zhixiangli:ci/subsystembenchmarks-stale-vm-cleanup
Jul 23, 2026
Merged

ci(subsystembenchmarks): harden stale VM cleanup#983
zhixiangli merged 2 commits into
fsspec:mainfrom
zhixiangli:ci/subsystembenchmarks-stale-vm-cleanup

Conversation

@zhixiangli

@zhixiangli zhixiangli commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

Summary

Adds an automated preflight cleanup step in the subsystem benchmark Cloud Build workflow to delete leaked VM instances older than 10 hours.

Changes

  • Added cleanup-leaked-resources step in subsystembenchmarks-cloudbuild.yaml that queries Compute Engine for VMs matching ${_INFRA_PREFIX}-vm- created more than 10 hours ago and deletes them.
  • Updated create-vm step to waitFor: ["cleanup-leaked-resources"] to prevent VM quota exhaustion before attempting to create a new VM.

@zhixiangli
zhixiangli requested a review from yuxin00j July 22, 2026 13:31

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request introduces a new cleanup-leaked-resources step in the Cloud Build configuration to automatically delete leaked VMs older than 10 hours before provisioning new ones. The review feedback suggests making the date parsing more robust by handling potential failures in date -d to prevent syntax errors during age calculation.

Comment thread cloudbuild/subsystembenchmarks/subsystembenchmarks-cloudbuild.yaml Outdated
@zhixiangli
zhixiangli merged commit 72d4061 into fsspec:main Jul 23, 2026
9 checks passed
@zhixiangli
zhixiangli deleted the ci/subsystembenchmarks-stale-vm-cleanup branch July 23, 2026 03:08
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.

2 participants