Skip to content

integration-cli: don't skip AppArmor tests on SLES#49061

Merged
thaJeztah merged 1 commit intomoby:masterfrom
cyphar:testing-suse-apparmor
Dec 16, 2024
Merged

integration-cli: don't skip AppArmor tests on SLES#49061
thaJeztah merged 1 commit intomoby:masterfrom
cyphar:testing-suse-apparmor

Conversation

@cyphar
Copy link
Copy Markdown
Contributor

@cyphar cyphar commented Dec 11, 2024

This partially reverts e440831 ("fix and skip some tests based on
API version"), which caused the integration-cli tests to skip all
AppArmor-related tests on SUSE.

It's not really clear why this was done originally, but I have verified
that on modern SLE 12 and SLE 15 systems the AppArmor tests pass without
any adjustments needed.

Signed-off-by: Aleksa Sarai [email protected]

This partially reverts e440831 ("fix and skip some tests based on
API version"), which caused the integration-cli tests to skip all
AppArmor-related tests on SUSE.

It's not really clear why this was done originally, but I have verified
that on modern SLE 12 and SLE 15 systems the AppArmor tests pass without
any adjustments needed.

Signed-off-by: Aleksa Sarai <[email protected]>
@thaJeztah
Copy link
Copy Markdown
Member

It's not really clear why this was done originally, but I have verified that on modern SLE 12 and SLE 15 systems the AppArmor tests pass without any adjustments needed.

Hm.. good one; I think that must've been related to docker enterprise which ISTR had to provide support for some very legacy version of SLES, so possibly(?) there was an issue in that version?

I want to look at some of the other changes in that PR though (#37003). If memory serves me well, those changes were related to an internal pipeline that was being set up to compile the integration tests and run them against various combinations of the daemon (and CLI). Looking at those changes though, there's some tests being excluded for API > 1.30, however the integration-cli suite is frozen (i.e., no new tests to be added that depend on the CLI, and instead test the API in this repository) and uses a fixed version (17.06) of the CLI. That version of the CLI only supports API 1.30 and older, so there should be no tests in there that depend on newer API versions 🤔

Copy link
Copy Markdown
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants