3.3 Upstream patches for storage #10111
Conversation
|
[testextended][extended:core] |
|
@stevekuznetsov the bot would appear to be disobedient |
|
@pmorie the trigger no longer contains |
…space deletion" issue
pmorie
changed the title
|
[test] |
|
@pmorie FYI the |
|
yup, I asked for the normal test suite |
| nodeName, | ||
| err) | ||
| return nil |
There was a problem hiding this comment.
return or continue? bigger question, should errors later in the loop return or continue?
There was a problem hiding this comment.
Yeah, I need to consider this. We will need a new PR to fix it anyway, so this can go in and we'll do another patch PR later.
There was a problem hiding this comment.
follow up issue upstream is fine
|
LGTM, I await the great flake deliverance with great anticipation |
|
Evaluated for origin testextended up to ca7c590 |
|
[merge] |
|
Evaluated for origin test up to ca7c590 |
|
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/7339/) (Image: devenv-rhel7_4718) |
|
Evaluated for origin merge up to ca7c590 |
|
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/7339/) |
|
Green test run |
|
continuous-integration/openshift-jenkins/testextended FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin_extended/385/) (Extended Tests: core) |
Needed to fix issues with secret and configmap mounts timing out.
First level is upstream cherry-pick, second level is upstream master PRs: