Revert "Skip all pasta tests"

[sbrivio-rh]

This reverts commit 81f116c: the passt package for Fedora 37 images is now fixed in the c20230223t153813z-f37f36d12 image.

Does this PR introduce a user-facing change?

None

[giuseppe]

LGTM

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: giuseppe, sbrivio-rh

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

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

[sbrivio-rh]

There's probably some other issue here, checking versions etc.

[sbrivio-rh]

@cevich the version of passt here is passt-0^20230216.g4663ccc-1.fc37-x86_64, instead of passt-0^20230222.g4ddbcb9-1.fc37, but c20230223t153813z-f37f36d12 is the IMAGE_SUFFIX in .cirrus.yml as you indicated. What am I doing wrong?

[sbrivio-rh]

@cevich the version of passt here is passt-0^20230216.g4663ccc-1.fc37-x86_64, instead of passt-0^20230222.g4ddbcb9-1.fc37, but c20230223t153813z-f37f36d12 is the IMAGE_SUFFIX in .cirrus.yml as you indicated. What am I doing wrong?

Never mind, my bad, I didn't commit that change.

[Luap99]

Thanks

/lgtm
/hold

[rhatdan]

Please remove WIP from heading if this is ready to merge.

[sbrivio-rh]

@Luap99 I guess you retriggered the "sys podman debian-12 rootless host" test, thanks! That failed twice with:

[+1305s] ok 497 podman networking with pasta(1) - UDP/IPv4 large transfer, tap
[11:59:07] END - [+1548s] total duration since 2023-02-28T11:59:07
Exit status: 2

...are the tests triggering a more general timeout, not for the specific test case? Let me know if there's anything I can debug.

Needless to say, I can consistently run these tests on current Debian Bookworm (current testing) with Podman and passt packages from Sid (unstable). :(

[sbrivio-rh]

@Luap99 I guess you retriggered the "sys podman debian-12 rootless host" test, thanks! That failed twice with:

[+1305s] ok 497 podman networking with pasta(1) - UDP/IPv4 large transfer, tap
[11:59:07] END - [+1548s] total duration since 2023-02-28T11:59:07
Exit status: 2

...are the tests triggering a more general timeout, not for the specific test case? Let me know if there's anything I can debug.

Needless to say, I can consistently run these tests on current Debian Bookworm (current testing) with Podman and passt packages from Sid (unstable). :(

Sorry, not my day. The re-run actually passed, I was following the wrong link.

[sbrivio-rh]

Please remove WIP from heading if this is ready to merge.

@rhatdan sure, I'm just waiting for a couple of tests to finish.

[Luap99]

I rerun "sys podman debian-12 rootless host" because of this error:

[+0683s] # (from function `is' in file test/system/helpers.bash, line 711,
[+0683s] #  in test file test/system/070-build.bats, line 957)
[+0683s] #   `is "$output"   "$dinode"   "COPY hardlinks work"' failed
[+0683s] # $ /var/tmp/go/src/github.com/containers/podman/bin/podman rm -t 0 --all --force --ignore
[+0683s] # $ /var/tmp/go/src/github.com/containers/podman/bin/podman ps --all --external --format {{.ID}} {{.Names}}
[+0683s] # $ /var/tmp/go/src/github.com/containers/podman/bin/podman images --all --format {{.Repository}}:{{.Tag}} {{.ID}}
[+0683s] # quay.io/libpod/testimage:20221018 f5a99120db64
[+0683s] # $ /var/tmp/go/src/github.com/containers/podman/bin/podman build -t build_test /tmp/podman_bats.OtAdAJ/build-test
[+0683s] # STEP 1/2: FROM quay.io/libpod/testimage:20221018
[+0683s] # STEP 2/2: COPY . /test
[+0683s] # COMMIT build_test
[+0683s] # --> 56f6defabb1
[+0683s] # Successfully tagged localhost/build_test:latest
[+0683s] # 56f6defabb1556f7c555c0fd35bb01e723763f3033e7f5cca2b867dc36ef459a
[+0683s] # $ /var/tmp/go/src/github.com/containers/podman/bin/podman run --rm build_test stat -c %i /test/Dockerfile
[+0683s] # 530185
[+0683s] # $ /var/tmp/go/src/github.com/containers/podman/bin/podman run --rm build_test stat -c %i /test/hardlink1
[+0683s] # 530184
[+0683s] # #/vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
[+0683s] # #|     FAIL: COPY hardlinks work
[+0683s] # #| expected: '530185'
[+0683s] # #|   actual: '530184'
[+0683s] # #\^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[+0683s] # $ /var/tmp/go/src/github.com/containers/podman/bin/podman rm -t 0 -a -f
[+0683s] # $ /var/tmp/go/src/github.com/containers/podman/bin/podman rmi -f build_test
[+0683s] # Untagged: localhost/build_test:latest
[+0683s] # Deleted: 56f6defabb1556f7c555c0fd35bb01e723763f3033e7f5cca2b867dc36ef459a
[+0683s] # $ /var/tmp/go/src/github.com/containers/podman/bin/podman image prune -f
[+0683s] # # [teardown]
[+0683s] # $ /var/tmp/go/src/github.com/containers/podman/bin/podman pod rm -t 0 --all --force --ignore
[+0683s] # $ /var/tmp/go/src/github.com/containers/podman/bin/podman rm -t 0 --all --force --ignore
[+0683s] # $ /var/tmp/go/src/github.com/containers/podman/bin/podman network prune --force
[+0683s] # $ /var/tmp/go/src/github.com/containers/podman/bin/podman volume rm -a -f

Seems to be a flake and unrelated to this change so I good with merging, if you saw actual timeouts in the pasta tests we should double check.

[sbrivio-rh]

Seems to be a flake and unrelated to this change so I good with merging, if you saw actual timeouts in the pasta tests we should double check.

No, no timeouts, I just saw a truncated log for a while, in the run you triggered it's all fine.

[Luap99]

ok
/hold cancel