all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Robert Vollmert <rob@vllmrt.net>
To: 36692@debbugs.gnu.org
Subject: [bug#36692] test failures
Date: Tue, 16 Jul 2019 18:00:51 +0200	[thread overview]
Message-ID: <1A10CE34-C9D6-4ECD-AA58-C7681043EBEF@vllmrt.net> (raw)
In-Reply-To: <20190716154734.22605-1-rob@vllmrt.net>

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"

  parent reply	other threads:[~2019-07-16 16:02 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 ` Robert Vollmert [this message]
2019-07-16 16:28   ` [bug#36692] test failures Marius Bakke
2019-07-16 16:36     ` Robert Vollmert
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

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

  git send-email \
    --in-reply-to=1A10CE34-C9D6-4ECD-AA58-C7681043EBEF@vllmrt.net \
    --to=rob@vllmrt.net \
    --cc=36692@debbugs.gnu.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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.