Linux SNPS ARC Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: fweimer@redhat.com (Florian Weimer)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH] testsuite fix: timezone: failing due to permissions in cross testing
Date: Tue, 18 Dec 2018 10:12:19 +0100	[thread overview]
Message-ID: <87a7l342rw.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1812172322060.9554@digraph.polyomino.org.uk> (Joseph Myers's message of "Mon, 17 Dec 2018 23:25:23 +0000")

* Joseph Myers:

> On Mon, 17 Dec 2018, Vineet Gupta wrote:
>
>> timezone test driver "zic" creates testdata directory wuth umask 755, so
>> only root owner/group has write permissions. However the buildroot
>
> root should not be involved in running tests at all; all tests should run 
> as a normal user, the same one that owns the build directory, and thus all 
> files and directories in the build directory should be owned by that user.
> (Some tests use user namespaces to test functionality that requires root, 
> but that's root inside a namespace, not the real user root.)

There are also some xtests that require root privileges, such as
nptl/tst-setuid1.  Building and testing as root is supported (but
obviously not recommended unless you use a throwaway machine).

Thanks,
Florian

  parent reply	other threads:[~2018-12-18  9:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17 23:09 [PATCH] testsuite fix: timezone: failing due to permissions in cross testing Vineet Gupta
2018-12-17 23:17 ` Paul Eggert
2018-12-17 23:23   ` Vineet Gupta
2018-12-17 23:25 ` Joseph Myers
2018-12-17 23:38   ` Vineet Gupta
2018-12-17 23:42     ` Joseph Myers
2018-12-18  9:12   ` Florian Weimer [this message]
2018-12-18 17:17     ` Joseph Myers
2019-01-09 12:15       ` Florian Weimer
2018-12-18 16:53   ` Vineet Gupta
  -- strict thread matches above, loose matches on Subject: below --
2018-12-17 23:04 Vineet Gupta

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

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

  git send-email \
    --in-reply-to=87a7l342rw.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=linux-snps-arc@lists.infradead.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox