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.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 8244 in the body.
You can then email your comments to 8244 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
owner <at> debbugs.gnu.org, bug-coreutils <at> gnu.org
:
bug#8244
; Package
coreutils
.
(Sun, 13 Mar 2011 18:36:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Каюков Андрей <andrka <at> yandex.ru>
:
New bug report received and forwarded. Copy sent to
bug-coreutils <at> gnu.org
.
(Sun, 13 Mar 2011 18:36:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/html, inline)]
[test-suite.log (text/x-log, attachment)]
Information forwarded
to
owner <at> debbugs.gnu.org, bug-coreutils <at> gnu.org
:
bug#8244
; Package
coreutils
.
(Mon, 14 Mar 2011 17:24:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 8244 <at> debbugs.gnu.org (full text, mbox):
retitle 8244 Test failures in coreutils 8.10
thanks
Thank you for the test failure report.
A message from Каюков Андрей was sent to the BTS but seems to have
been lost before making it to the bug-coreutils outgoing mailing list.
Thanks to Eric Blake who noticed this and alerted me to the problem.
The original message is available in the BTS.
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8244
Here is a plain text summary. Please see the test-suite.log file
attached to the BTS for the full 90K test log file.
==============================================
GNU coreutils 8.10: tests/test-suite.log
==============================================
7 of 14 tests failed. (9 tests were not run).
FAIL: cp/special-bits (exit: 1)
FAIL: cp/sparse-fiemap (exit: 1)
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)
Changed bug title to 'Test failures in coreutils 8.10' from 'Please report to bug-coreutils <at> gnu.org'
Request was from
Bob Proulx <bob <at> proulx.com>
to
control <at> debbugs.gnu.org
.
(Mon, 14 Mar 2011 17:24:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
owner <at> debbugs.gnu.org, bug-coreutils <at> gnu.org
:
bug#8244
; Package
coreutils
.
(Mon, 14 Mar 2011 22:29:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 8244 <at> debbugs.gnu.org (full text, mbox):
On 14/03/11 17:23, Bob Proulx wrote:
> retitle 8244 Test failures in coreutils 8.10
> thanks
>
> Thank you for the test failure report.
>
> A message from Каюков Андрей was sent to the BTS but seems to have
> been lost before making it to the bug-coreutils outgoing mailing list.
> Thanks to Eric Blake who noticed this and alerted me to the problem.
> The original message is available in the BTS.
>
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8244
>
> Here is a plain text summary. Please see the test-suite.log file
> attached to the BTS for the full 90K test log file.
>
> ==============================================
> GNU coreutils 8.10: tests/test-suite.log
> ==============================================
>
> 7 of 14 tests failed. (9 tests were not run).
>
FAIL: cp/sparse-fiemap (exit: 1)
This one is an issue with the test already addressed upstream
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.
thanks,
Pádraig.
Reply sent
to
Jim Meyering <jim <at> meyering.net>
:
You have taken responsibility.
(Wed, 16 Mar 2011 05:55:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
Каюков Андрей <andrka <at> yandex.ru>
:
bug acknowledged by developer.
(Wed, 16 Mar 2011 05:55:02 GMT)
Full text and
rfc822 format available.
Message #18 received at 8244-done <at> debbugs.gnu.org (full text, mbox):
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.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 13 Apr 2011 11:24:04 GMT)
Full text and
rfc822 format available.
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.