-
Notifications
You must be signed in to change notification settings - Fork 45
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
Test failures when built in minimal container #261
Comments
test-copy: test-user-util: test-cgroup: |
If elogind is built in a minimal container, cg_unified_cached() might return -ENOENT instead of -ENOMEDIUM. Bug: #261 Signed-off-by: Sven Eden <sven@eden-worx.com>
If elogind is built in a minimal container, cg_unified_cached() might return -ENOENT instead of -ENOMEDIUM. Bug: #261 Signed-off-by: Sven Eden <sven@eden-worx.com>
If elogind is built in a minimal container, cg_unified_cached() might return -ENOENT instead of -ENOMEDIUM. Bug: #261 Signed-off-by: Sven Eden <sven@eden-worx.com>
There's indeed no /var/tmp in the container, just /tmp. |
I confirm that using |
Fixed in both v255 and v252.23 |
Hi! I just tried 255.4-r2 with Guix, and this is what I get so far:
Some failures are due to expecting FHS file names, but I still see some cgroup-related failures there. |
Hi,
Building the latest version 252.9, I see these test new failures:
test-copy now fais for unknown reason. The build machine uses the Btrfs file system, in case that can have an effect.
test-user-util fails because there's no user
root
in the build containers (other tests assuming such user exists are already skipped in Guix).test-cgroup fails because
/sys/fs/cgroup/
is not exposed in the build container.Perhaps the test suite could be made to check for these assumptions and mark the tests that rely on them as skipped when they aren't met.
The text was updated successfully, but these errors were encountered: