You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like #297 was merged w/o passing CI tests. I'm not sure why/how all the CI tests there are marked "Canceled" - maybe b/c renovate tried to update the PR just as merge button was clicked? Either way, the previous run also failed CI in the same way.
py36: install_deps> pip install -r /var/tmp/go/src/github.com/containers/podman-py/test-requirements.txt
Could not find a version that satisfies the requirement fixtures~=4.1.0 (from -r /var/tmp/go/src/github.com/containers/podman-py/test-requirements.txt (line 5)) (from versions: 0.1, 0.2, 0.3, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.3.5, 0.3.6, 0.3.7, 0.3.8, 0.3.9, 0.3.10, 0.3.11, 0.3.12, 0.3.13, 0.3.14, 0.3.15, 0.3.16, 0.3.17, 1.0.0, 1.1.0, 1.2.0, 1.2.1, 1.3.0, 1.3.1, 1.3.2.dev6, 1.4.0, 2.0.0, 3.0.0, 4.0.0, 4.0.1)
No matching distribution found for fixtures~=4.1.0 (from -r /var/tmp/go/src/github.com/containers/podman-py/test-requirements.txt (line 5))
...cut...
pylint: OK (26.62=setup[15.11]+cmd[11.51] seconds)
coverage: OK (64.43=setup[19.68]+cmd[44.28,0.47] seconds)
py36: FAIL code 1 (4.54 seconds)
py38: OK (60.40=setup[20.35]+cmd[40.05] seconds)
py39: OK (59.85=setup[20.48]+cmd[39.38] seconds)
py310: OK (59.62=setup[19.69]+cmd[39.93] seconds)
py311: OK (55.21=setup[15.19]+cmd[40.03] seconds)
evaluation failed :( (333.95 seconds)
@rhatdan or @umohnani8 any idea what we should do here? For CI, maybe we could somehow tell CI for 3.6 to use the old version? Otherwise clearly this will (at a minimum) fail to run RHEL (due to fixtures incompatibility with 3.6). A more drastic option (but likely to work) is to revert that commit.
The text was updated successfully, but these errors were encountered:
It looks like #297 was merged w/o passing CI tests. I'm not sure why/how all the CI tests there are marked "Canceled" - maybe b/c renovate tried to update the PR just as merge button was clicked? Either way, the previous run also failed CI in the same way.
Anyway, this change is now failing CI tests on main. Looks like a python-3.6 incompatibility. That means every PR opened or rebased with this changed will also fail CI.
@rhatdan or @umohnani8 any idea what we should do here? For CI, maybe we could somehow tell CI for 3.6 to use the old version? Otherwise clearly this will (at a minimum) fail to run RHEL (due to fixtures incompatibility with 3.6). A more drastic option (but likely to work) is to revert that commit.
The text was updated successfully, but these errors were encountered: