-
Notifications
You must be signed in to change notification settings - Fork 43
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
Five tests error/fail in a testing chroot on Linux with bizarre error messages #67
Comments
OK, I think I've figured this one out: because my chroot is mounted as an overlay filesystem, def find_mount_point(path):
# Even if something's wrong, "/" is a mount point, so the loop will exit.
# Use realpath in case it's a symlink
path = op.realpath(path) # Required to avoid infinite loop
while not op.ismount(path) or op.isfile(path): # Note ismount() does not always detect mounts
path = op.split(path)[0]
return path (noting the extra |
BTW, this patch fixes the issue and shouldn't change the behaviour of the function in "normal" situations, so it may be worth applying. |
No, I spoke too soon; the test: topdir = find_mount_point(path_b)
trash_dev = get_dev(topdir)
if trash_dev != path_dev:
raise OSError("Couldn't find mount point for %s" % path) causes an |
Yeah, I have found a workaround to actually get mounts better than what ismount() does but it relies on other utilities being available on the system and running them essentially from the script. I really did not like that, even though it utilized utilities which were almost always present on systems. I can take a bit of a look at this case, as a similar case was encountered (partially the reason for the 1.8.1b0 version), and was at least able to be handled better. As for your bit about the home environment, send2trash looks for |
Indeed! I'm not sure, though, that "fixing" the topdir tests will help even then, as the chances are that the user won't have write permission to create the I have tried finding a workaround, but sadly to no avail; in the chroot overlay setup, creating a directory in |
I guess the only other way of resolving this is to make the modification to |
Oh, that didn't work either: it just ended up trying to create |
Coming back to this with the same issue I previously posted here.
|
Hi!
As part of the Debian build, the package tests are run in a minimal chroot environment. I've set the
HOME
environment variable first:The thing that seems so weird to me is the strange filenames/directories it's trying to work with, such as
b'/tmp/s2t9qns8us6/subdir/test.txt/.Trash-1000'
. It strikes me that something has gone wrong in the calculation of the trash directory name. (And there's no sign of theHOME
directory I so carefully set up!)The text was updated successfully, but these errors were encountered: