KEMBAR78
Storage retry by BenWhitehead · Pull Request #51 · googleapis/conformance-tests · GitHub
Skip to content

Conversation

@BenWhitehead
Copy link
Collaborator

No description provided.

@google-cla google-cla bot added the cla: yes This human has signed the Contributor License Agreement. label Jul 20, 2021
@BenWhitehead BenWhitehead requested a review from tritone August 5, 2021 21:32
@BenWhitehead BenWhitehead marked this pull request as ready for review August 5, 2021 21:32
Copy link
Contributor

@tritone tritone left a comment

Choose a reason for hiding this comment

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

Thanks for updating this!

}

log.Printf("Validating: %v/%v", dir, f.Name())
if strings.Contains(f.Name(), "v4_signatures.json") {
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe we can just make a map between the expected jsons and protos and use that, rather than iterating through the directory?

Also, does this get run in the CI for this repo?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I cleaned things up a little bit, so they're at least sharing some logic. Not sure if you were hoping for something else.

Yeah, CI does run. The Kokoro CI status runs the validation programs.

Copy link
Contributor

@tritone tritone left a comment

Choose a reason for hiding this comment

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

One nit, otherwise LGTM

@BenWhitehead BenWhitehead merged commit 37ddc58 into googleapis:master Aug 19, 2021
@BenWhitehead BenWhitehead deleted the storage-retry branch August 19, 2021 23:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants