From: Robert Vollmert <rob@vllmrt.net>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 36692@debbugs.gnu.org
Subject: [bug#36692] test failures
Date: Tue, 16 Jul 2019 18:36:35 +0200 [thread overview]
Message-ID: <7CE61390-AB3B-42B9-B453-3C9D1FDD10D2@vllmrt.net> (raw)
In-Reply-To: <87tvbm54gm.fsf@devup.no>
> On 16. Jul 2019, at 18:28, Marius Bakke <mbakke@fastmail.com> wrote:
>
> Robert Vollmert <rob@vllmrt.net> writes:
>
>> I was able to run both tests from the build directory in /tmp,
>> and they both passed fine. Also they both involve user ids, I
>> suspect those might differ in the build container?
>>
>> main = do
>> void $ forkIO $ forever $ getGroupEntryForID 0
>> void $ forkIO $ forever $ getGroupEntryForID 0
>> threadDelay (3*1000*1000)
>>
>> main = do
>> root <- getUserEntryForName "root"
>> putStrLn (ue2String root)
>> root' <- getUserEntryForID (userID root)
>> putStrLn (ue2String root')
>> if homeDirectory root == homeDirectory root' &&
>> userShell root == userShell root'
>> then putStrLn "OK"
>> else putStrLn “Mismatch"
>
> The only reliable user ID available in the build container is 'nobody'
> with UID and GID 65534 and the (see nix/libstore/build.cc:1862).
>
> You can likely patch these tests to refer to that instead.
Thanks, I’ll give that a shot!
There’s something I don’t understand: Comments above the definition
of ghc-7 mention test failures, particularly one of these (posix010):
;; - Test posix010 tries to check the existence of a user on the system:
;; getUserEntryForName: does not exist (no such user)
But I don’t see any place in the definitions of any of the GHC packages
(ghc-7, ghc-8.0, ghc-8.4) that patch any tests out, and tests aren’t
disabled either. So how can these packages apparently be fine?
next prev parent reply other threads:[~2019-07-16 16:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 15:47 [bug#36692] [PATCH 0/2] Add GHC 8.6.5 Robert Vollmert
2019-07-16 15:48 ` [bug#36692] [PATCH 1/2] gnu: Rename ghc-8 to ghc-8.4 Robert Vollmert
2019-07-16 15:48 ` [bug#36692] [PATCH 2/2] gnu: Add GHC 8.6.5 Robert Vollmert
2019-07-16 16:00 ` [bug#36692] test failures Robert Vollmert
2019-07-16 16:28 ` Marius Bakke
2019-07-16 16:36 ` Robert Vollmert [this message]
2019-07-16 16:45 ` Marius Bakke
2019-07-16 19:00 ` Robert Vollmert
2019-07-16 18:58 ` [bug#36692] [PATCH 1/2] gnu: ghc@8.6.5: Duplicate build arguments from ghc-8.4 Robert Vollmert
2019-07-16 18:58 ` [bug#36692] [PATCH 2/2] gnu: ghc@8.6.5: Skip failing tests Robert Vollmert
2019-07-16 19:47 ` [bug#36692] [PATCH (unified, replaces previous patches)] gnu: Add GHC 8.6.5 Robert Vollmert
2019-08-08 4:26 ` bug#36692: " Timothy Sample
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=7CE61390-AB3B-42B9-B453-3C9D1FDD10D2@vllmrt.net \
--to=rob@vllmrt.net \
--cc=36692@debbugs.gnu.org \
--cc=mbakke@fastmail.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).