CI: disable ginkgo flake retries

[edsantiago]

As discussed in Aug 13 Cabal, we are almost at a point where
e2e tests are reliably passing on the first try. Let's try to
keep things that way, and not hide future flakes.

Closes: #17967

Signed-off-by: Ed Santiago santiago@redhat.com

None

[packit-as-a-service]

We were not able to find or create Copr project packit/containers-podman-23662 specified in the config with the following error:

Packit received HTTP 500 Internal Server Error from Copr Service. Check the Copr status page: https://copr.fedorainfracloud.org/status/stats/, or ask for help in Fedora Build System matrix channel https://matrix.to/#/#buildsys:fedoraproject.org.

---

Unless the HTTP status code above is >= 500, please check your configuration for:

1. typos in owner and project name (groups need to be prefixed with @)
2. whether the project name doesn't contain not allowed characters (only letters, digits, underscores, dashes and dots must be used)
3. whether the project itself exists (Packit creates projects only in its own namespace)
4. whether Packit is allowed to build in your Copr project
5. whether your Copr project/group is not private

[Luap99]

You will need to rebase (#23614), Macos lint is failing on all other main PRs (not sure why this broke but my lint update should fix it)

[edsantiago]

Consensus was to file this as soon as #22246 closed.

Currently open flakes that we can expect to see:

• podman exec into a "-it" container: container create failed (no logs from conmon): EOF #10927 - super frustrating. Vanishes for months, then hits three times in three days.
• flakey/broken detection of criu version #18856 - criu version weirdness, rare
• e2e: network scoped DNS server test: nslookup write: ECONNREFUSED #18890 (may be fixed once we upgrade aardvark-dns in CI VMs)
• composefs: random EINVALs #23385 - composefs

[Luap99]

LGTM

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: edsantiago, Luap99

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

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

[rhatdan]

@edsantiago Ok if you want this....
/lgtm