To proceed with https://pagure.io/pagure/pull-request/5463 I need to disable F39 RPM test runs and pass the REPO and BRANCH env var to podman build. Without the env vars, pagure.io/pagure.git:master will always be used. Changes to files like dev/containers/tox_py3.sh, dev/containers/runtests_py3.sh or files/pagure.spec are never taken into account during a PR CI run.
F39pipisn't affected, but on rpm the tests stucktill the OOM Killer triggers. There are multiplesimilar reports upstream but no fix. To unblockthe unit tests, F39 RPM will be skipped for now.F39 pip covers py39, py310, py311 and py312.CI jobs that run into the issue:https://jenkins-pagure.apps.ocp.cloud.ci.centos.org/job/pull-requests/276/https://jenkins-pagure.apps.ocp.cloud.ci.centos.org/job/pull-requests/277/GitHub issues that report similar issues:https://github.com/pytest-dev/pytest-xdist/issues/110https://github.com/pytest-dev/pytest-xdist/issues/661https://github.com/pytest-dev/pytest-xdist/issues/872https://github.com/pytest-dev/pytest-xdist/issues/1005
To proceed with https://pagure.io/pagure/pull-request/5463 I need to disable F39 RPM test runs and pass the REPO and BRANCH env var to podman build. Without the env vars,
pagure.io/pagure.git:masterwill always be used. Changes to files likedev/containers/tox_py3.sh,dev/containers/runtests_py3.shorfiles/pagure.specare never taken into account during a PR CI run.