try github actions failure to see if PRs can't be merged

[rifelpet]

Ref: #9005

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rifelpet

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [rifelpet]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[rifelpet]

@mikesplain would prow merge this if it had a lgtm label? looking at the tide details, it seems like it would but i'd expect it not to.

[hakman]

/lgtm

[rifelpet]

🥁
the tide page isn't mentioning the GHA failures but i guess we'll see if it is able to merge it or not. I'm guessing not given that the GHA jobs now have the Required label on them.

If it can't merge it, then we can close this and proceed with #9005

[rifelpet]

:(

[mikesplain]

Right... I think because prow doesn't know about them... which is why https://github.com/kubernetes/test-infra/pull/17917/files#diff-00deeeaf0a7a2aba7d06744db0da6d43R535-R536 is needed.

[hakman]

Do we want also to skip unknown contexts?
https://github.com/kubernetes/test-infra/blob/c68834a35762399bac39eff4bbcef65cb5b9fd12/config/prow/config.yaml#L529-L530

[rifelpet]

that seems strange because the GHA jobs are now showing as "required" in the list of statuses:

so i would think that GH wouldn't let prow merge the PR even if it wanted to... ah well, we can resume this when you get a chance to test more on your internal prow

[mikesplain]

Unknown contexts didn't work as expected when I tested it.

Tide doesn't do a github merge afaik. It does it all via git commands essentially. But tide blocks on jobs it knows about and, when configured, protected branch rules.

I'll revisit that PR later in the week to see if I can figure it out. Next time I wish we could get some logs before immediately reverting.