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

[BUG] S3/GCS tests use same staging directory for each test #539

Open
ai-bq opened this issue Feb 13, 2023 · 0 comments
Open

[BUG] S3/GCS tests use same staging directory for each test #539

ai-bq opened this issue Feb 13, 2023 · 0 comments
Labels
bug Something isn't working ci Management of the continuous integration pipeline Low Priority

Comments

@ai-bq
Copy link
Collaborator

ai-bq commented Feb 13, 2023

Recently upon attempting to run the Weekly tests for both Java 11 and 8 it was discovered that the S3/GCS tests for 11 and 8 cannot run at the same time due to the fact that the staging directory is the same throughout each test.

It was since decided that Java 8 only needed it's own end to end test and all though the GCS/S3 tests are functional and passing, the end to ends should have unique staging directories in case of issues in the future.

One of the failed weekly tests can be seen here.

In particular:

Array("***/94d9f456_dd4c_45b8_860c_4957e902b697") was not empty. After each test, staging directory should be cleaned.
@ai-bq ai-bq added bug Something isn't working Low Priority ci Management of the continuous integration pipeline labels Feb 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ci Management of the continuous integration pipeline Low Priority
Projects
None yet
Development

No branches or pull requests

1 participant