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

Add shyamjvs to test/OWNERS #55319

Merged

Conversation

shyamjvs
Copy link
Member

@shyamjvs shyamjvs commented Nov 8, 2017

I've been reviewing quite some PRs recently and have reviewed many in the past. + I have >80 commits in this code path (git log test | grep "shyamjvs@google.com") touching various parts including e2e/framework, utils, perftype, kubemark, e2e fixes from other SIGs (mostly in regard of scalability).

/cc @gmarek @spiffxp @krzyzacy @kubernetes/sig-testing-misc

@k8s-ci-robot
Copy link
Contributor

@shyamjvs: Adding do-not-merge/release-note-label-needed because the release note process has not been followed.

One of the following labels is required "release-note", "release-note-action-required", or "release-note-none".
Please see: https://github.com/kubernetes/community/blob/master/contributors/devel/pull-requests.md#write-release-notes-if-needed.

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.

@k8s-ci-robot k8s-ci-robot added retest-not-required-docs-only sig/testing Categorizes an issue or PR as relevant to SIG Testing. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Nov 8, 2017
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Nov 8, 2017
@shyamjvs shyamjvs requested a review from gmarek November 8, 2017 14:50
@shyamjvs shyamjvs added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Nov 8, 2017
@k8s-ci-robot
Copy link
Contributor

@shyamjvs: Adding do-not-merge/release-note-label-needed because the release note process has not been followed.

One of the following labels is required "release-note", "release-note-action-required", or "release-note-none".
Please see: https://github.com/kubernetes/community/blob/master/contributors/devel/pull-requests.md#write-release-notes-if-needed.

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.

@k8s-ci-robot k8s-ci-robot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. and removed release-note-none Denotes a PR that doesn't merit a release note. labels Nov 8, 2017
@shyamjvs shyamjvs added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Nov 8, 2017
@gmarek
Copy link
Contributor

gmarek commented Nov 8, 2017

+1 on that, but I'd like to get a second approval from someone from @kubernetes/sig-testing-misc. @spiffxp?

@fejta
Copy link
Contributor

fejta commented Nov 8, 2017

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 8, 2017
@spiffxp
Copy link
Member

spiffxp commented Nov 8, 2017

What do you think about OWNERS files in the specific directories you mentioned rather than at the top level of test?

@spiffxp
Copy link
Member

spiffxp commented Nov 8, 2017

eg:

spiffxp@kthxbye:kubernetes (master %)$ for path in \
$(git log --follow --name-only --author="Shyam Jeedigunta" test | grep ^test | sort | uniq); do\
  dirname $path; \
done | uniq -c
   1 test/e2e
   1 test/e2e/apimachinery
   3 test/e2e/common
   3 test/e2e
   7 test/e2e/framework
   1 test/e2e/kubectl
   2 test/e2e/perf
   5 test/e2e/scalability
   3 test/kubemark
   1 test/kubemark/common
   1 test/kubemark
   1 test/kubemark/gce
   2 test/kubemark
   4 test/kubemark/resources
   4 test/kubemark/resources/manifests/addons/kubemark-rbac-bindings
   6 test/kubemark/resources/manifests
   1 test/kubemark/resources
   1 test/kubemark
   1 test/kubemark/skeleton
   2 test/kubemark
   1 test/utils

@shyamjvs
Copy link
Member Author

shyamjvs commented Nov 8, 2017

They don't have individual owners files. For e.g e2e, e2e/framework. Seems like it's only the SIG directories that're having them.

@krzyzacy
Copy link
Member

krzyzacy commented Nov 8, 2017

/retest

@krzyzacy
Copy link
Member

krzyzacy commented Nov 8, 2017

lgtm, 😂 obviously our test-infra folks cannot approve for you here

@shyamjvs
Copy link
Member Author

shyamjvs commented Nov 8, 2017

@fejta / @gmarek Could one of you /approve no-issue this?

@spiffxp
Copy link
Member

spiffxp commented Nov 8, 2017

/approve no-issue
I guess I'd rather not blow scope here, and I've seen you put in the time. But this does look a clear cut case of where we (collectively) should be adding new OWNERS files for the leaves, and taking people out of the test/ dir where possible. Now that you're getting added to test/OWNERS, you have the power to do this, so that you wouldn't get assigned to all PR's that touch test/*

@k8s-github-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fejta, shyamjvs, spiffxp

Associated issue requirement bypassed by: spiffxp

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these OWNERS Files:

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

@k8s-github-robot k8s-github-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 8, 2017
@shyamjvs
Copy link
Member Author

shyamjvs commented Nov 8, 2017

Yup.. I agree :)

@fejta fejta mentioned this pull request Nov 8, 2017
@fejta
Copy link
Contributor

fejta commented Nov 8, 2017

Aaron 100% agree with that instinct. Filed a bug to do this separately.

@shyamjvs
Copy link
Member Author

shyamjvs commented Nov 8, 2017

/retest

@shyamjvs
Copy link
Member Author

shyamjvs commented Nov 8, 2017

@fejta Any reason why you've removed the retest-not-required label?

@fejta
Copy link
Contributor

fejta commented Nov 8, 2017

Yes, please leave retest labels off PRs as it just slows down the overall merge rate as it invalidates batch merges.

@k8s-github-robot
Copy link

Automatic merge from submit-queue (batch tested with PRs 55301, 55319, 54018, 55322, 55125). If you want to cherry-pick this change to another branch, please follow the instructions here.

@k8s-github-robot k8s-github-robot merged commit 6257541 into kubernetes:master Nov 9, 2017
@shyamjvs shyamjvs deleted the add-shyamjvs-to-test-owners branch November 9, 2017 11:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants