Bug#751575: adt-virt-schroot: fails to replicate tests which pass elsewhere
retitle 751575 schroot fails with /dev/fd/62: No such file or directory
thanks
Hey Neil,
Neil Williams [2014-06-14 13:46 +0100]:
> E: Can not write log (Is /dev/pts mounted?) - openpty (2: No such file or directory)
> Setting up adt-satdep (0) ...
This error from apt might be insightful: Which profile does your
schroot use, and what is your corresponding
/etc/schroot/<profile>/fstab ?
I use the "default" profile for my schroots which bind-mounts /dev/,
/dev/pts, and /dev/shm.
The "sbuild" profile still bind-mounts /dev/pts, so I suppose you are
using something else.
However, even if I comment out /dev/pts from
/etc/schroot/sbuild/fstab, I do get this error from apt (which doesn't
stop autopkgtest), but I still don't get the main error:
> adt-run [2014-06-14 13:39:52]: & apt0t-testsuite: [-----------------------
> bash: line 10: /dev/fd/62: No such file or directory
I think the most likely explanation for this is that your schroot
doesn't have /proc bind-mounted, as /dev/fd is usually a symlink to
/proc/self/fd (please double-check in your schroot).
If I comment out the /proc bind mount from /etc/schroot/*/profile, I
get exactly the same error.
If you use any kind of nontrivial stdin/out/err redirections in
dash/bash that will use /dev/fd/ rather heavily. A lot of other stuff
will also fail without /proc/ in your schroot, so I'm rather surprised
that you never noticed that?
So to guard against this I could add an explicit test for
"bind-mounted /proc" to the schroot runner; but a schroot without
/proc is rather useless, so it's a bit of a surprise that folks have
them in the first place :-)
Thanks,
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/autopkgtest-devel/attachments/20140615/5dd7f07e/attachment.sig>
Reply to: