System tests: emergency skip of checkpoint tests

[edsantiago]

...on kernel 5.17, because it's broken. Needed for gating tests on rawhide.

Signed-off-by: Ed Santiago [email protected]

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: edsantiago

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 [edsantiago]

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

[Luap99]

LGTM

[rhatdan]

/hold
/lgtm

[edsantiago]

@cevich any idea what's going on here? The Total Success is red. Clicking on it claims that the new remote rootless task failed, but it didn't, it shows as green here. This has been stuck for at least 30m.

[rhatdan]

I forced merge it.

[cevich]

The Total Success is red.

Damn...that's not right...investigating...

[cevich]

it shows as green here

Yeah, don't always believe the status reported by github. There is a (still) long open bug where it doesn't match what the CI system reports (especially after a re-run). This bug even affects github-actions...no idea why they refuse/can't fix it. Anyway, clicking on it now (in Cirrus WebUI) does show a failure (flake I think):

[+0414s] not ok 182 podman kill - test signal handling in containers
...cut...
[+0414s] # #/vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
[+0414s] # #| FAIL: Timed out: no ACK for kill -s 25
[+0414s] # #\^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

[edsantiago]

I saw that too. However, looking at the CI results on github itself (both in the Conversation tab and the Checks one) shows all tests green, including the allegedly-failing one. My gut feel is that the test flaked, someone restarted it, then it passed, but Cirrus didn't get the memo that the test passed on rerun. I manually confirmed that the test did pass. I also compared task IDs (or job IDs or whatever, the long number starting with 6) and they were different.

[cevich]

Wait, you're right (re-run theory) this is somehow a mixup in Cirrus-CI, look closely at the build page: https://cirrus-ci.com/build/5960543587532800 There are TWO entries for sys remote fedora-35 rootless host. One red, one green. I'll let support know about this, it should never happen.