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.

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

Not all databases are cleaned up after an integration test run #2819

Open
olavloite opened this issue Jan 26, 2024 · 0 comments
Open

Not all databases are cleaned up after an integration test run #2819

olavloite opened this issue Jan 26, 2024 · 0 comments
Assignees
Labels
api: spanner Issues related to the googleapis/java-spanner API. type: process A process-related concern. May include testing, release, or the like.

Comments

@olavloite
Copy link
Collaborator

Databases that are created during an integration test run are not all deleted. This causes RESOURCE_EXHAUSTED errors to pop up in the builds after a while, and the databases need to be manually deleted before getting the builds green again. We should:

  1. Check all integration tests for any databases that are created, but not deleted afterwards.
  2. Implement an automatic clean-up job at the start of each integration test run that scans for test databases with a known name format, and then delete the databases that are older than X time.
@olavloite olavloite added the type: process A process-related concern. May include testing, release, or the like. label Jan 26, 2024
@product-auto-label product-auto-label bot added the api: spanner Issues related to the googleapis/java-spanner API. label Jan 26, 2024
@arpan14 arpan14 assigned rahul2393 and unassigned arpan14 Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: spanner Issues related to the googleapis/java-spanner API. type: process A process-related concern. May include testing, release, or the like.
Projects
None yet
Development

No branches or pull requests

3 participants