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
1.48.5: test_file_architecture_26 and test_xfs_growfs_0 failing #100
Comments
signal 24 may be SIGXCPU, indicating some sort of crash. Not sure what to say about this, but it might be significant that the test involves a zstd file which we only added support for recently. Is it reproducible if you run This is a bug (of sorts) caused by changing requirements again in xfs. Our test disk was only 40MB. I will see if I can fix this. |
I cannot reproduce the originally reported error: libguestfs: error: mkfs: xfs: /dev/VG/LV: Filesystem must be larger than 300MB. Thanks: David Runge Related: #100
That seems fine (outside of the build environment): |
|
Thanks. Another thing to try would be something like: I expect that the last command may segfault for you inside the appliance, although I don't know why. |
|
Hmm, that actually also went fine (in the build environment): |
|
During the build the test still fails though. btw: Your patch for |
|
Ah, I guess it would be |
Add upstream patch for failing test and disable other failing test: libguestfs/libguestfs#100 git-svn-id: file:///srv/repos/svn-community/svn@1351897 9fca08f4-af9d-4005-b8df-a31f2cc04f65
Add upstream patch for failing test and disable other failing test: libguestfs/libguestfs#100 git-svn-id: file:///srv/repos/svn-community/svn@1351897 9fca08f4-af9d-4005-b8df-a31f2cc04f65
|
Right, although I'm confused/worried why that test is failing ... |
|
Let me know if I can test further things. Build/test always takes quite a while (even on my machine) but I can try again tomorrow. |
|
It's probably the 'z' switch: Arch compiles its "file" utility with seccomp support whereas it appears Fedora does not. At least that's what it looks like after checking the koji build log: Is that intentional by Fedora? |
|
Oh, well spotted! This could well be the case. Let me compile the Fedora package with seccomp support to see if I can reproduce the problem ... |
|
Yes, I can reproduce this. In fact this is both a bug upstream (in the seccomp support) and in Fedora. I will file bugs for both. |
|
Upstream bug: https://bugs.astron.com/view.php?id=406 |
|
re: the upstream report...not sure that'll fly as it's kinda expected when the sandbox is in effect. See the man page [1]. The libguestfs test can be made to pass if the "file" call on line 46 of daemon/file.ml is changed from "-zb" to "-zbS", but I'm not sure if that's what you really want. |
The file(1) manual suggests using -S (disable seccomp) with -z since the set of system calls provided by the seccomp policy does not allow the subprocess to run. This is obvious when you use file -z on a compressed file on a Linux distro that enables file's seccomp policy (Arch does this, Fedora does not): $ file -zbsL lib-i586.so.zst Bad system call I also fixed some incorrect text in the manual. Thanks: Toolybird for pointing to this fix Reported-by: David Runge Fixes: #100 (cherry picked from commit 23986d3)
Hi! While packaging 1.48.5 for Arch Linux I ran into these two tests failing:
test_file_architecture_26andtest_xfs_growfs_0.libguestfs-1.48.5-1-x86_64-build.log
libguestfs-1.48.5-1-x86_64-check.log
test-suite.log
The text was updated successfully, but these errors were encountered: