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
Bug 1781283: Set resource requests on the extract job #276
Bug 1781283: Set resource requests on the extract job #276
Conversation
@smarterclayton: An error was encountered adding this pull request to the external tracker bugs for bug 1781283 on the Bugzilla server at https://bugzilla.redhat.com:
Please contact an administrator to resolve this issue, then request a bug refresh with In response to this:
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. |
We want to be in burstable QoS, and we want to avoid causing warnings if e2e runs detect that we happen to be running when they see we aren't in burstable.
62bf86f
to
f9f5cd7
Compare
/bugzilla refresh |
@sdodson: An error was encountered adding this pull request to the external tracker bugs for bug 1781283 on the Bugzilla server at https://bugzilla.redhat.com:
Please contact an administrator to resolve this issue, then request a bug refresh with In response to this:
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. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, smarterclayton The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
/bugzilla refresh |
@abhinavdahiya: An error was encountered adding this pull request to the external tracker bugs for bug 1781283 on the Bugzilla server at https://bugzilla.redhat.com:
Please contact an administrator to resolve this issue, then request a bug refresh with In response to this:
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. |
@smarterclayton: All pull requests linked via external trackers have merged. Bugzilla bug 1781283 has been moved to the MODIFIED state. In response to this:
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. |
/cherry-pick release-4.3 |
@smarterclayton: new pull request could not be created: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between openshift:release-4.3 and openshift-cherrypick-robot:cherry-pick-276-to-release-4.3"}],"documentation_url":"https://developer.github.com/v3/pulls/#create-a-pull-request"} In response to this:
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. |
Oh, already backported.
…On Thu, Dec 12, 2019 at 12:25 AM OpenShift Cherrypick Robot < ***@***.***> wrote:
@smarterclayton <https://github.com/smarterclayton>: new pull request
could not be created: status code 422 not one of [201], body:
{"message":"Validation
Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No
commits between openshift:release-4.3 and
openshift-cherrypick-robot:cherry-pick-276-to-release-4.3"}],"documentation_url":"
https://developer.github.com/v3/pulls/#create-a-pull-request"}
In response to this
<#276 (comment)>
:
/cherry-pick release-4.3
Instructions for interacting with me using PR comments are available here
<https://git.k8s.io/community/contributors/guide/pull-requests.md>. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#276?email_source=notifications&email_token=AAI37JZYZKNRMXJ5FUKJWITQYHDMBA5CNFSM4JYNELKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGVQC5Y#issuecomment-564855159>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAI37J2BGIJTXO4WWUMCT5DQYHDMBANCNFSM4JYNELKA>
.
|
We want to be in burstable QoS, and we want to avoid causing warnings
if e2e runs detect that we happen to be running when they see we
aren't in burstable.