Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Automated cherry pick of #36623 #36789

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Nov 15, 2016
Merged

Automated cherry pick of #36623 #36789

merged 1 commit into from
Nov 15, 2016

Conversation

yujuhong
Copy link
Contributor

@yujuhong yujuhong commented Nov 15, 2016 •
edited by k8s-oncall
Loading

Cherry pick of #36623 on release-1.4.

#36623: Use generous limits in the resource usage tracking tests

This change is Reviewable

@yujuhong
Use generous limits in the resource usage tracking tests
2d5b3b7 
These tests are mainly used to catch resource leaks in the soak cluster. Using
higher limits to reduce noise.
@yujuhong
Copy link
Contributor Author

This doesn't disable the test, but should still fix #32320 and the test failures in #32214

@yujuhong yujuhong added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Nov 15, 2016
@yujuhong yujuhong added this to the v1.4 milestone Nov 15, 2016
@k8s-github-robot k8s-github-robot added do-not-merge DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Nov 15, 2016
@k8s-ci-robot
Copy link
Contributor

Jenkins GCE etcd3 e2e failed for commit 2d5b3b7. Full PR test history.

The magic incantation to run this job again is @k8s-bot gce etcd3 e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

@jessfraz jessfraz added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. cherrypick-candidate lgtm "Looks good to me", indicates that a PR is ready to be merged. and removed do-not-merge DEPRECATED. Indicates that a PR should not merge. Label can only be manually applied/removed. retest-not-required labels Nov 15, 2016
@jessfraz
Copy link
Contributor

thanks! I have added the labels!

@yujuhong
Copy link
Contributor Author

@k8s-bot gce etcd3 e2e test this

@k8s-github-robot
Copy link

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

@k8s-github-robot
Copy link

Automatic merge from submit-queue

@k8s-github-robot k8s-github-robot merged commit 1ef1217 into kubernetes:release-1.4 Nov 15, 2016
@k8s-cherrypick-bot
Copy link

Commit found in the "release-1.4" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked.

This was referenced Nov 15, 2016
Closed
Closed
shyamjvs pushed a commit to shyamjvs/kubernetes that referenced this pull request Dec 1, 2016
Merge pull request kubernetes#36789 from yujuhong/automated-cherry-pi…
b856fe2 
…ck-of-#36623-upstream-release-1.4

Automatic merge from submit-queue

Automated cherry pick of kubernetes#36623

Cherry pick of kubernetes#36623 on release-1.4.

kubernetes#36623: Use generous limits in the resource usage tracking tests
@yujuhong yujuhong deleted the automated-cherry-pick-of-#36623-upstream-release-1.4 branch March 13, 2017 17:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@jessfraz jessfraz

@dchen1107 dchen1107

Labels
cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Milestone
v1.4
Development

Successfully merging this pull request may close these issues.
7 participants
@yujuhong @k8s-ci-robot @jessfraz @k8s-github-robot @k8s-cherrypick-bot @googlebot @dchen1107