Closed shiftstack-merge-bot[bot] closed 2 years ago
/ok-to-test
/retest
/lgtm
Seems like a timeout to get a pod created, nothing too serious. I'll leave the approval to another person though.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dulek, shiftstack-merge-bot[bot]
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Okay, I'll leave the override to somebody else then.
/retest-required
Remaining retests: 0 against base HEAD b99369f6bbaa5addbea2f8f4d01b69147413b624 and 2 for PR HEAD 35a33090d0888596dba8c3c7e2d282c2b9eee4bc in total
/override ci/prow/e2e-openstack-kuryr
The test failure [sig-network] pods should successfully create sandboxes by adding pod to network
is not caused by this PR. Our periodic jobs also fail with it and we will analyze it. So, I'm overriding CI.
@MaysaMacedo: Overrode contexts on behalf of MaysaMacedo: ci/prow/e2e-openstack-kuryr
@shiftstack-merge-bot[bot]: all tests passed!
Full PR test history. Your PR dashboard.
Hi @shiftstack-merge-bot[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.