GNU bug report logs -
#8244
Test failures in coreutils 8.10
Previous Next
Reported by: Каюков Андрей <andrka <at> yandex.ru>
Date: Sun, 13 Mar 2011 18:36:02 UTC
Severity: normal
Done: Jim Meyering <jim <at> meyering.net>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Wed, 16 Mar 2011 06:54:07 +0100
with message-id <871v271ugw.fsf <at> rho.meyering.net>
and subject line Re: bug#8244: Test failures in coreutils 8.10
has caused the GNU bug report #8244,
regarding Test failures in coreutils 8.10
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
8244: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8244
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
[Message part 3 (text/html, inline)]
[test-suite.log (text/x-log, attachment)]
[Message part 5 (message/rfc822, inline)]
Pádraig Brady wrote:
...
> FAIL: misc/chroot-credentials (exit: 1)
> FAIL: misc/truncate-owned-by-other (exit: 1)
> FAIL: mv/sticky-to-xpart (exit: 1)
> FAIL: rm/no-give-up (exit: 1)
> FAIL: touch/now-owned-by-other (exit: 1)
> FAIL: cp/special-bits (exit: 1)
>
> The above 6 are all due to the same issue,
> that the "nobody" user is not allowed to execute stuff,
> as demonstrated by this in one of the tests:
>
> $ chroot --userspec=nobody:99 / whoami
> chroot: failed to run command `whoami': Permission denied
>
> This seems unusual to me.
> It will help us decide if we need to skip these tests in this case,
> if you could detail the credentials on your system preventing
> "nobody" from executing these programs.
That is typically what happens when you run "sudo make check-root"
without setting NON_ROOT_USERNAME as suggested in README:
**********************
Running tests as root:
----------------------
If you run the tests as root, note that a few of them create files
and/or run programs as a non-root user, `nobody' by default.
If you want to use some other non-root username, specify it via
the NON_ROOT_USERNAME environment variable. Depending on the
permissions with which the working directories have been created,
using `nobody' may fail, because that user won't have the required
read and write access to the build and test directories.
I find that it is best to unpack and build as a non-privileged
user, and then to run the following command as that user in order
to run the privilege-requiring tests:
sudo env PATH="$PATH" NON_ROOT_USERNAME=$USER make -k check-root
If you can run the tests as root, please do so and report any
problems. We get much less test coverage in that mode, and it's
arguably more important that these tools work well when run by
root than when run by less privileged users.
I've marked this issue as closed,
but if you have additional comments or reason
to think it should not be closed, feel free to
continue the discussion and/or reopen the issue.
This bug report was last modified 14 years and 74 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.