-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
cloud: use uuid as bucket name #135595
cloud: use uuid as bucket name #135595
Conversation
80aa5e0
to
b0ce78a
Compare
This PR depends on #135619. The roll back and the fix need to be in two different PRs so the fix applies cleanly in all backports. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
might be best to kick off another cloud nightly
Previously, the GCS and S3 tests used hard coded bucket names to test the behavior of buckets that do not exist. Now, the tests use a random UUID. This change is necessary because someone appears to have created the GCP bucket which causes the test to fail. Release Justification: Test Only Change Release Note: None Fixes: cockroachdb#135307 Fixes: cockroachdb#135348 Fixes: cockroachdb#135349 Fixes: cockroachdb#135350 Fixes: cockroachdb#135351 Fixes: cockroachdb#135352
b0ce78a
to
627c9ac
Compare
The cloud azure test is failing, but that seems to be independent of this change. |
Thanks for the review! |
Previously, the GCS and S3 tests used hard coded bucket names to test
the behavior of buckets that do not exist. Now, the tests use a random
UUID. This change is necessary because someone appears to have created
the GCP bucket which causes the test to fail.
Release Justification: Test Only Change
Release Note: None
Fixes: #135307
Fixes: #135348
Fixes: #135349
Fixes: #135350
Fixes: #135351
Fixes: #135352