Skip to content

Conversation

@fish98
Copy link
Contributor

@fish98 fish98 commented Feb 2, 2023

The introduction of FuzzIntegNoTearDownWithDownload is confusing with the duplicate names in container fuzzer.

Signed off by: Jiongchi Yu [email protected]

@k8s-ci-robot
Copy link

Hi @fish98. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Comment on lines 398 to 400
// FuzzNoTearDownWithDownload() implements a fuzzer
// similar to FuzzCreateContainerNoTearDown() and
// FuzzCreateContainerWithTearDown(), but it takes a
Copy link
Member

Choose a reason for hiding this comment

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

It looks like I've missed some history here, since this isn't the only one where it isn't matching, but the function name is FuzzIntegNoTearDownWithDownload, not FuzzNoTearDownWithDownload.

For this to fit conventional Go style, it'd also need to change like this:

Suggested change
// FuzzNoTearDownWithDownload() implements a fuzzer
// similar to FuzzCreateContainerNoTearDown() and
// FuzzCreateContainerWithTearDown(), but it takes a
// FuzzIntegNoTearDownWithDownload implements a fuzzer
// similar to FuzzIntegCreateContainerNoTearDown and
// FuzzIntegCreateContainerWithTearDown, but it takes a

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks for your review. I have rechecked the whole file following your suggestion, and updated the rest of the function names :)

Copy link
Member

@estesp estesp left a comment

Choose a reason for hiding this comment

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

LGTM

@fish98
Copy link
Contributor Author

fish98 commented Feb 7, 2023

/retest

@k8s-ci-robot
Copy link

@fish98: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kzys
Copy link
Member

kzys commented Feb 9, 2023

/ok-to-test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants