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
enable sample imagestreams and templates on Z #225
Conversation
40b8099
to
25ff9dd
Compare
/retest |
25ff9dd
to
7ef85e0
Compare
/retest |
7ef85e0
to
768cc7b
Compare
/test e2e-aws-operator |
/test e2e-aws-jenkins |
need openshift/origin#24434 for e2e-aws-jenkins |
/test e2e-aws-jenkins |
1 similar comment
/test e2e-aws-jenkins |
768cc7b
to
1c3e828
Compare
ok @pweil- @bparees @adambkaplan @ausil @yselkowitz here is my original version of the unlock s390/ppc commit (which I had pointed @yselkowitz to), along with the s390x/ppc64le content from openshift/library which we just merged/processed We can either use this PR (associating it with @yselkowitz's BZs to facilitate backports) or he can duplicate this in his. Per our meeting, placing a /hold on this until we get the comeback on the test coverage. In the interim, I'll monitor the e2e's in case any non-CI flakes/issues occur. |
/test unit |
1c3e828
to
a352d7d
Compare
/test unit |
/test e2e-aws-operator |
/retest |
/test e2e-aws-operator |
/test e2e-aws-jenkins |
ok finally got a clean jenkins install, but of course are now running into the need for openshift/origin#24448 |
/retest |
/retest Please review the full test history for this PR and help us cut down flakes. |
in ci-flake cycle ... pulling out of merge queue, try to let CI settle /hold |
/test e2e-aws-builds |
/retest |
@akram @waveywaves it looks like one of the 3 changes between to 2 of you to Perhaps related to you all trying to get the test passing in earlier versions of OCP (4.2 / 4.3 / 4.4) ? /hold cancel |
/override e2e-aws-builds |
/override e2e-aws-jenkins |
@gabemontero: /override requires a failed status context to operate on.
Only the following contexts were expected:
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. |
1 similar comment
@gabemontero: /override requires a failed status context to operate on.
Only the following contexts were expected:
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. |
@gabemontero: /override requires a failed status context to operate on.
Only the following contexts were expected:
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. |
1 similar comment
@gabemontero: /override requires a failed status context to operate on.
Only the following contexts were expected:
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. |
/override ci/prow/e2e-aws-builds |
everything else in e2e-aws-builds passed in the last run of it and had prior clean runs prior to the recent changes in https://github.com/openshift/jenkins-client-plugin/commits/master/examples/jenkins-image-sample.groovy hence chose ot use override |
@gabemontero: Overrode contexts on behalf of gabemontero: ci/prow/e2e-aws-builds, ci/prow/e2e-aws-jenkins 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. |
1 similar comment
@gabemontero: Overrode contexts on behalf of gabemontero: ci/prow/e2e-aws-builds, ci/prow/e2e-aws-jenkins 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.5 |
@yselkowitz: only openshift org members may request cherry picks. You can still do the cherry-pick manually. 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. |
1 similar comment
@yselkowitz: only openshift org members may request cherry picks. You can still do the cherry-pick manually. 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. |
ack @gabemontero |
@gabemontero: An error was encountered updating to the MODIFIED state for bug 1850694 on the Bugzilla server at https://bugzilla.redhat.com:
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. |
@gabemontero: All pull requests linked via external trackers have merged: . Bugzilla bug 1850694 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. |
No description provided.