Closed ghost closed 2 years ago
Hi @kuryr-bot. Thanks for your PR.
I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
/ok-to-test
/retest
@kuryr-bot: The following test failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
ci/prow/e2e-openstack-kuryr | 48a60a381ac9d165bb20355ac33f355d4266ef2a | link | true | /test e2e-openstack-kuryr |
Full PR test history. Your PR dashboard.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: kuryr-bot To complete the pull request process, please assign dulek after the PR has been reviewed. You can assign the PR to them by writing
/assign @dulek
in a comment when ready.The full list of commands accepted by this bot can be found here.