Skip to content
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

Jump to bottom

The Clean Up GCP Resources job is flaky #31846

Open
github-actions bot opened this issue Jul 11, 2024 · 10 comments
Open

The Clean Up GCP Resources job is flaky #31846

github-actions bot opened this issue Jul 11, 2024 · 10 comments
Labels
bug flaky_test P1 workflow_id: 70196931
Milestone
2.63.0 Release

Comments

@github-actions
Copy link
Contributor

The Clean Up GCP Resources is failing over 80% of the time.
Please visit https://github.com/apache/beam/actions/workflows/beam_CleanUpGCPResources.yml?query=is%3Afailure+branch%3Amaster to see all failed workflow runs.
See also Grafana statistics: http://metrics.beam.apache.org/d/CTYdoxP4z/ga-post-commits-status?orgId=1&viewPanel=1&var-Workflow=Clean%20Up%20GCP%20Resources
@Abacn
Copy link
Contributor

Abacn commented Jul 11, 2024

there are more "Tried and failed to delete bq_read_all_" and other datasets. Likely related to recent python test workflow failure, which used a different service account to run tests

@github-actions github-actions bot added this to the 2.59.0 Release milestone Aug 20, 2024
@github-actions github-actions bot reopened this Aug 22, 2024
@github-actions GitHub Actions
Copy link
Contributor Author

Reopening since the workflow is still flaky

@Abacn
Copy link
Contributor

Abacn commented Aug 22, 2024

due to 2.58.1 validation Python PostCommits run again without #31955 and leaked dataset

@Abacn Abacn closed this as completed Aug 22, 2024
@github-actions github-actions bot reopened this Oct 2, 2024
@github-actions GitHub Actions
Copy link
Contributor Author

github-actions bot commented Oct 2, 2024

Reopening since the workflow is still flaky

@Abacn
Copy link
Contributor

Abacn commented Oct 2, 2024

cleaned up stale instances

@Abacn Abacn modified the milestones: 2.60.0 Release, 2.61.0 Release Oct 2, 2024
@damccorm damccorm closed this as completed Oct 3, 2024
@github-actions github-actions bot reopened this Dec 20, 2024
@github-actions GitHub Actions
Copy link
Contributor Author

Reopening since the workflow is still flaky

@Abacn Abacn closed this as completed Dec 30, 2024
@github-actions github-actions bot reopened this Jan 1, 2025
@github-actions GitHub Actions
Copy link
Contributor Author

github-actions bot commented Jan 1, 2025

Reopening since the workflow is still flaky

@damccorm
Copy link
Contributor

damccorm commented Jan 7, 2025

Cleaned up some stale resources, got a green run

@damccorm damccorm closed this as completed Jan 7, 2025
@github-actions github-actions bot reopened this Jan 9, 2025
@github-actions GitHub Actions
Copy link
Contributor Author

github-actions bot commented Jan 9, 2025

Reopening since the workflow is still flaky

@Abacn
Copy link
Contributor

Abacn commented Jan 9, 2025

It has been a recurring issue: #33435

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug flaky_test P1 workflow_id: 70196931
Projects
None yet
Milestone
2.63.0 Release
Development

No branches or pull requests
2 participants
@Abacn @damccorm