Closed jasonbrooks closed 2 years ago
/ok-to-test /override peribolos
@HumairAK: /override requires a failed status context or a job name to operate on. The following unknown contexts were given:
peribolos
Only the following contexts were expected:
tide
apologies, looks like this went under the radar
/retest /override peribolos
@HumairAK: Overrode contexts on behalf of HumairAK: community-management/prow/peribolos
/override peribolos
@tumido: Failed to get presubmits
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: tumido
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/unhold
This has been a journey! Let me know if I did something wrong, or if there's something I need to fix. :)
@jasonbrooks for context there is an ongoing issue with our peribolos configurations, I believe @tumido is using this pr as a test case while he tries to fix the issues.
Hey, sorry for the mess, I had to cleanup some of the broken config that got merged in before for some reason. I hope it will be working already just to merge yours and then I've noticed some more broken stuff. :smile: :smirk: I've also modified your PR to list your GH handle instead of jbrooks
- that wouldn't work. :slightly_smiling_face: I'll continue investigating the issue and eventually merge this in. Sorry again.
/test all
Hi @jasonbrooks. Thanks for your PR.
I'm waiting for a operate-first 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.