unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: mikadoZero <mikadozero@yandex.com>
Cc: 35047@debbugs.gnu.org
Subject: bug#35047: "Running the Test Suite" root user
Date: Sat, 30 Mar 2019 14:50:35 +0100	[thread overview]
Message-ID: <874l7ka2ve.fsf@nckx> (raw)
In-Reply-To: <cuc5zs05y0z.fsf@yandex.com>

[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]

mikadoZero,

mikadoZero wrote:
> Looking at "2.3 Running the Test Suite" of the manual it does 
> not
> mention that tests should be run as a non root user.

I guess this is one of those (Unix-)cultural knowledge things: it 
wouldn't even occur to me to build or test anything as root unless 
explicitly asked to do so :-)

> The test `tests/pack` fails when `make check` is run as a root 
> user.  It
> does not fail when run as a non root user.  I found this example 
> by
> running `make check TESTS="tests/pack.scm"`.  Is this an issue 
> for many
> tests?
>
> I can prepare a patch for the relevant part (parts if this also 
> applies
> to `make check-system` as well) in "2.3 Running the Test Suite" 
> of the
> manual.

Thanks for the offer!  I think adding yet another gotcha to the 
manual should be a last resort, though.  Many people still miss 
them and get into trouble (and on to IRC).

Could we, in order of preference:

- make these tests pass even when run as root?  (I guess not?)
- skip them and add ‘n tests not run as root’ to the final tally?
- refuse to even start the test suite as root?

What ‘root’ means here will depend on why these tests are failing.

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2019-03-30 13:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-30 12:47 bug#35047: "Running the Test Suite" root user mikadoZero
2019-03-30 13:50 ` Tobias Geerinckx-Rice [this message]
2019-03-30 15:30   ` mikadoZero

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874l7ka2ve.fsf@nckx \
    --to=me@tobias.gr \
    --cc=35047@debbugs.gnu.org \
    --cc=mikadozero@yandex.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).