Automated cherry pick of #63631: Add gpu cluster upgrade test. #64842
Conversation
|
@jiayingz: All 'parent' PRs of a cherry-pick PR must have one of the "release-note" or "release-note-action-required" labels, or this PR must follow the standard/parent release note labeling requirement. The following parent PRs have neither the "release-note" nor the "release-note-action-required" labels: #63631. 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
added
the
size/L
|
@jiayingz: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. 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
added
the
do-not-merge/release-note-label-needed
k8s-github-robot
added
the
do-not-merge/cherry-pick-not-approved
k8s-ci-robot
added
the
cncf-cla: yes
|
/assign @mindprince @vishh @krzyzacy |
|
/assign @MaciekPytel |
|
/release-note-none |
k8s-ci-robot
added
release-note-none
|
/test pull-kubernetes-integration |
MaciekPytel
added
cherry-pick-approved
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jiayingz, vishh 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 |
k8s-ci-robot
added
the
approved
|
/remove-priority important-longterm |
k8s-ci-robot
removed
the
priority/important-longterm
|
/priority critical-urgent |
k8s-ci-robot
added
priority/critical-urgent
|
[MILESTONENOTIFIER] Milestone Pull Request: Up-to-date for process @MaciekPytel @jiayingz @krzyzacy @mindprince @vishh Pull Request Labels
|
|
/retest Review the full test history for this PR. Silence the bot with an |
5 similar comments
|
/retest Review the full test history for this PR. Silence the bot with an |
|
/retest Review the full test history for this PR. Silence the bot with an |
|
/retest Review the full test history for this PR. Silence the bot with an |
|
/retest Review the full test history for this PR. Silence the bot with an |
|
/retest Review the full test history for this PR. Silence the bot with an |
|
/test pull-kubernetes-verify |
|
/retest Review the full test history for this PR. Silence the bot with an |
2 similar comments
|
/retest Review the full test history for this PR. Silence the bot with an |
|
/retest Review the full test history for this PR. Silence the bot with an |
|
I think this is an actual issue in the code. The verify test is
consistently failing.
…On Sun, Jun 10, 2018 at 9:38 AM k8s-ci-robot ***@***.***> wrote:
@jiayingz <https://github.com/jiayingz>: The following test *failed*, say
/retest to rerun them all:
Test name Commit Details Rerun command
pull-kubernetes-verify 339a04a
<339a04a>
link
<https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/64842/pull-kubernetes-verify/95038/> /test
pull-kubernetes-verify
Full PR test history <https://k8s-gubernator.appspot.com/pr/64842>. Your
PR dashboard <https://k8s-gubernator.appspot.com/pr/jiayingz>. Please
help us cut down on flakes by linking to
<https://git.k8s.io/community/contributors/devel/flaky-tests.md#filing-issues-for-flaky-tests>
an open issue
<https://github.com/kubernetes/kubernetes/issues?q=is:issue+is:open> when
you hit one in your PR.
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. I understand the commands that are listed here
<https://go.k8s.io/bot-commands>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#64842 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAqb-srckHJz4CWa5hkVuTz5rhP424Frks5t7UucgaJpZM4UdDCL>
.
|
|
/retest Review the full test history for this PR. Silence the bot with an |
6 similar comments
|
/retest Review the full test history for this PR. Silence the bot with an |
|
/retest Review the full test history for this PR. Silence the bot with an |
|
/retest Review the full test history for this PR. Silence the bot with an |
|
/retest Review the full test history for this PR. Silence the bot with an |
|
/retest Review the full test history for this PR. Silence the bot with an |
|
/retest Review the full test history for this PR. Silence the bot with an |
|
@jiayingz yep, it appears fixed now. |
|
/test all [submit-queue is verifying that this PR is safe to merge] |
|
Automatic merge from submit-queue. |
Cherry pick of #63631 on release-1.10.
#63631: Add gpu cluster upgrade test.
We added a gpu upgrade test config from 1.9-1.10 (kubernetes/test-infra#8262). From the test logs, looks like the cluster upgrade test is using the e2e test version from the latest 1.10 release which doesn't have the newly added GPUUpgrade test. There doesn't seem to be an easy way to use the e2e test version from a head release while running the upgrade test for older release version. Cherry-picking the upgrade test to 1.10 branch so that we can gpu upgrade test from 1.9 to 1.10.