Testing against podman-next breaks test_container_mounts #547
Assignees
Labels
bug
Something isn't working
Comments
|
cc: @lsm5 |
A better solution could be to duplicate the tests runs and run the test suite against distribution |
inknos
added a commit
to inknos/podman-py
that referenced
this issue
May 2, 2025
1. Split upstream into distro/pnext test runs A new CI run targets tests that are exclusive for podman-next. /upstream plans are now split into /distro and /pnext to be explicit against which podman version is used in the tests. Also, python version used are now called base_python and all_python, to be more self explainatory. 2. Add pytest marker `pnext` to filter tests Tests that should run against podman-next are now skipped by default in tox runs. They can be enabled with --pnext and filtered in using `-m pnext`. These two options should be used together since `pnext` and `non-pnext` tests are thought to be incompatible. 3. Split `test_container_mounts` to test a breaking change and update docs The scenario `test_container_mounts` was split to demonstrates the usage of the marker against an upstream breaking change. CONTRIBUTING.md now reflects the new feature and explains how to use tox locally to leverage on this feature. Fixes: containers#547 Signed-off-by: Nicola Sella <[email protected]>
inknos
added a commit
to inknos/podman-py
that referenced
this issue
May 2, 2025
1. Split upstream into distro/pnext test runs A new CI run targets tests that are exclusive for podman-next. /upstream plans are now split into /distro and /pnext to be explicit against which podman version is used in the tests. Also, python version used are now called base_python and all_python, to be more self explainatory. 2. Add pytest marker `pnext` to filter tests Tests that should run against podman-next are now skipped by default in tox runs. They can be enabled with --pnext and filtered in using `-m pnext`. These two options should be used together since `pnext` and `non-pnext` tests are thought to be incompatible. 3. Split `test_container_mounts` to test a breaking change and update docs The scenario `test_container_mounts` was split to demonstrates the usage of the marker against an upstream breaking change. CONTRIBUTING.md now reflects the new feature and explains how to use tox locally to leverage on this feature. Fixes: containers#547 Signed-off-by: Nicola Sella <[email protected]>
inknos
added a commit
to inknos/podman-py
that referenced
this issue
May 2, 2025
1. Split upstream into distro/pnext test runs
A new CI run targets tests that are exclusive for podman-next.
/upstream plans are now split into /distro and /pnext to be explicit
against which podman version is used in the tests. Also, python version
used are now called base_python and all_python, to be more self
explainatory.
2. Add pytest marker `pnext` to filter tests
Tests that should run against podman-next are now skipped by default in
tox runs. They can be enabled with --pnext and filtered in using
`-m pnext`. These two options should be used together since `pnext` and
`non-pnext` tests are thought to be incompatible.
3. Split `test_container_mounts` to test a breaking change and update
docs
The scenario `test_container_mounts` was split to demonstrates the
usage of the marker against an upstream breaking change.
CONTRIBUTING.md now reflects the new feature and explains how to use tox
locally to leverage on this feature.
4. Add manual trigger on packit
Since the tests cover a corner case and serve the purpose of testing
unreleased features of libpod (which is slightly out of the scope of
podman-py) the testing jobs are optional and should run for certain PRs
only. The command to run the pnext tests is the following.
/packit test --labels {pnext,podman_next}
Fixes: containers#547
Signed-off-by: Nicola Sella <[email protected]>
inknos
added a commit
to inknos/podman-py
that referenced
this issue
May 2, 2025
1. Split upstream into distro/pnext test runs
A new CI run targets tests that are exclusive for podman-next.
/upstream plans are now split into /distro and /pnext to be explicit
against which podman version is used in the tests. Also, python version
used are now called base_python and all_python, to be more self
explainatory.
2. Add pytest marker `pnext` to filter tests
Tests that should run against podman-next are now skipped by default in
tox runs. They can be enabled with --pnext and filtered in using
`-m pnext`. These two options should be used together since `pnext` and
`non-pnext` tests are thought to be incompatible.
3. Split `test_container_mounts` to test a breaking change and update
docs
The scenario `test_container_mounts` was split to demonstrates the
usage of the marker against an upstream breaking change.
CONTRIBUTING.md now reflects the new feature and explains how to use tox
locally to leverage on this feature.
4. Add manual trigger on packit
Since the tests cover a corner case and serve the purpose of testing
unreleased features of libpod (which is slightly out of the scope of
podman-py) the testing jobs are optional and should run for certain PRs
only. The command to run the pnext tests is the following.
/packit test --labels {pnext,podman_next}
Fixes: containers#547
Signed-off-by: Nicola Sella <[email protected]>
inknos
added a commit
to inknos/podman-py
that referenced
this issue
May 2, 2025
1. Split upstream into distro/pnext test runs
A new CI run targets tests that are exclusive for podman-next.
/upstream plans are now split into /distro and /pnext to be explicit
against which podman version is used in the tests. Also, python version
used are now called base_python and all_python, to be more self
explainatory.
2. Add pytest marker `pnext` to filter tests
Tests that should run against podman-next are now skipped by default in
tox runs. They can be enabled with --pnext and filtered in using
`-m pnext`. These two options should be used together since `pnext` and
`non-pnext` tests are thought to be incompatible.
3. Split `test_container_mounts` to test a breaking change and update
docs
The scenario `test_container_mounts` was split to demonstrates the
usage of the marker against an upstream breaking change.
CONTRIBUTING.md now reflects the new feature and explains how to use tox
locally to leverage on this feature.
4. Add manual trigger on packit
Since the tests cover a corner case and serve the purpose of testing
unreleased features of libpod (which is slightly out of the scope of
podman-py) the testing jobs are optional and should run for certain PRs
only. The command to run the pnext tests is the following.
/packit test --labels {pnext,podman_next}
Fixes: containers#547
Signed-off-by: Nicola Sella <[email protected]>
inknos
added a commit
to inknos/podman-py
that referenced
this issue
May 2, 2025
1. Split upstream into distro/pnext test runs
A new CI run targets tests that are exclusive for podman-next.
/upstream plans are now split into /distro and /pnext to be explicit
against which podman version is used in the tests. Also, python version
used are now called base_python and all_python, to be more self
explainatory.
2. Add pytest marker `pnext` to filter tests
Tests that should run against podman-next are now skipped by default in
tox runs. They can be enabled with --pnext and filtered in using
`-m pnext`. These two options should be used together since `pnext` and
`non-pnext` tests are thought to be incompatible.
3. Split `test_container_mounts` to test a breaking change and update
docs
The scenario `test_container_mounts` was split to demonstrates the
usage of the marker against an upstream breaking change.
CONTRIBUTING.md now reflects the new feature and explains how to use tox
locally to leverage on this feature.
4. Add manual trigger on packit
Since the tests cover a corner case and serve the purpose of testing
unreleased features of libpod (which is slightly out of the scope of
podman-py) the testing jobs are optional and should run for certain PRs
only. The command to run the pnext tests is the following.
/packit test --labels {pnext,podman_next}
Fixes: containers#547
Signed-off-by: Nicola Sella <[email protected]>
inknos
added a commit
to inknos/podman-py
that referenced
this issue
May 5, 2025
1. Split upstream into distro/pnext test runs
A new CI run targets tests that are exclusive for podman-next.
/upstream plans are now split into /distro and /pnext to be explicit
against which podman version is used in the tests. Also, python version
used are now called base_python and all_python, to be more self
explainatory.
2. Add pytest marker `pnext` to filter tests
Tests that should run against podman-next are now skipped by default in
tox runs. They can be enabled with --pnext and filtered in using
`-m pnext`. These two options should be used together since `pnext` and
`non-pnext` tests are thought to be incompatible.
3. Split `test_container_mounts` to test a breaking change and update
docs
The scenario `test_container_mounts` was split to demonstrates the
usage of the marker against an upstream breaking change.
CONTRIBUTING.md now reflects the new feature and explains how to use tox
locally to leverage on this feature.
4. Add manual trigger on packit
Since the tests cover a corner case and serve the purpose of testing
unreleased features of libpod (which is slightly out of the scope of
podman-py) the testing jobs are optional and should run for certain PRs
only. The command to run the pnext tests is the following.
/packit test --labels {pnext,podman_next}
Fixes: containers#547
Signed-off-by: Nicola Sella <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This recent upstream breaking change impacted the tests containers/podman#25942.
Probably podman-py testing should reflect only podman release branches
Impacts:
#513
#544
#546
#540
And other test runs
The text was updated successfully, but these errors were encountered: