-
Notifications
You must be signed in to change notification settings - Fork 2.9k
more BATS tests #4824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
more BATS tests #4824
Conversation
|
[Test failure was because podman-remote does not emit "Trying to pull ..." messages; so there's no way to distinguish I-pulled from image-was-already-here. Decided to just |
$ ./bin/podman run --rm --privileged --userns=host quay.io/libpod/alpine_labels:latest cat -v /proc/self/attr/current
WARNING: The same type, major and minor should not be used for multiple devices.Any ideas? |
|
It's not a flake: rerunning fails the same way. There's something weird about the f30 test image, and I suspect it's a real problem. Unfortunately it will be almost impossible to debug. I've submitted opencontainers/runtime-tools#701 as a long-term future way of getting a slight clue about what's wrong, but even if that's accepted (which is unlikely because its CI is failing and I have no idea why) it would take time to vendor this into podman. |
|
Maybe I'm missing something, but I'm not seeing the warning when I run it "by hand" on my F30 vm with upstream Podman. However the output is missing a carriage return, it couldn't be that could it? |
|
No, it works fine (no warning message) on all the f30 systems I've tried. The problem is something specific to the CI one. (And no, it's not the NUL-instead-of-NL terminator. That's just the way |
jwhonce
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM when tests pass
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: edsantiago, jwhonce The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
sudo podman run --rm --privileged quay.io/libpod/alpine_labels:latest cat -v /proc/self/attr/current Something is wacky with --privileged. Looks like a bug. |
|
Well the good thing, is this bug exists with older podman. podman run --privileged alpine echo hello rpm -q podman |
|
Added a little extra ouput WARNING: The same type, major and minor should not be used for multiple devices. /dev/null Looks like we have two |
|
Looks like the way my host was configured. |
- run: --name (includes 'podman container exists' tests) - run: --pull (always, never, missing) - build: new test for ADD URL (containers#4420) - exec: new test for issue containers#4785 (pipe getting lost) - diff: new test - selinux (mostly copied from docker-autotest) Plus a bug fix: the wait_for_output() helper would continue checking, eventually timing out, even if the container had already exited (probably because of an error). Fix: as part of the loop, run 'podman inspect' and bail out if container is not running. Include exit code and logs. Signed-off-by: Ed Santiago <[email protected]>
|
opencontainers/runtime-tools#701 is merged, so some day we'll get greater visibility into what the problem is, but that could take years (new runtime-tools release, then a podman revendor). ITM I've simply special-cased the warning and ignored it. The warning will still appear in test logs, in case anyone wants to fix it, but the selinux test will not fail because of it. |
|
/lgtm |
Plus a bug fix: the wait_for_output() helper would continue
checking, eventually timing out, even if the container had
already exited (probably because of an error). Fix: as
part of the loop, run 'podman inspect' and bail out if
container is not running. Include exit code and logs.
Signed-off-by: Ed Santiago [email protected]