Yes, probably the best to disable it for now. On Fri, Sep 26, 2014 at 11:43 AM, Thomas Miedema <[email protected]> wrote: > Hi, > >> The user001 is tracked by this bug: >> https://ghc.haskell.org/trac/ghc/ticket/1487 > > > This is my fault. I made a patch that reenabled that test some time ago, but > it fails under certain conditions. I just proposed a proper solution to the > libraries mailinglist. We could also disable the test now, if you don't want > to wait at least another 2 weeks. > > With apologies, > Thomas > > >> >> >> Excerpts from Simon Peyton Jones's message of 2014-09-26 04:37:59 -0700: >> > I am getting one persistent failure on Linux: >> > >> > >> > =====> user001(normal) 5 of 29 [0, 0, 0] >> > >> > cd . && '/5playpen/simonpj/HEAD-2/inplace/bin/ghc-stage2' -fforce-recomp >> > -dcore-lint -dcmm-lint -dno-debug-output -no-user-package-db -rtsopts >> > -fno-ghci-history -o user001 user001.hs -package unix >> > >user001.comp.stderr >> > 2>&1 >> > >> > cd . && ./user001 >user001.run.stdout 2>user001.run.stderr >> > >> > Actual stdout output differs from expected: >> > >> > --- ./user001.stdout 2014-09-11 08:38:41.000000000 +0100 >> > >> > +++ ./user001.run.stdout 2014-09-26 12:29:52.363884118 +0100 >> > >> > @@ -3,11 +3,11 @@ >> > >> > getEffectiveUserID: OK >> > >> > getEffectiveGroupID: OK >> > >> > getGroups: OK >> > >> > -getLoginName: OK >> > >> > +getLoginName: ERROR: getLoginName: does not exist (No such file or >> > directory) >> > >> > getEffectiveUserName: OK >> > >> > getGroupEntryForID: OK >> > >> > getGroupEntryForName: OK >> > >> > getAllGroupEntries: OK >> > >> > getUserEntryForID: OK >> > >> > -getUserEntryForName: OK >> > >> > +getUserEntryForName: ERROR: getLoginName: does not exist (No such file >> > or directory) >> > >> > getAllUserEntries: OK >> > >> > *** unexpected failure for user001(normal) >> > >> > This is in libraries/unix/tests. >> > >> > I am also getting two failures when I say "sh validate" (runs in >> > parallel). But when I run them individually, they pass: >> > ghci/should_run T2589 [bad stdout or stderr] (ghci) >> > ghci/should_run ghcirun004 [bad stdout or stderr] (ghci) >> > >> > >> > +++ ./ghci/should_run/ghcirun004.run.stderr 2014-09-26 >> > 12:06:21.102269076 +0100 >> > >> > @@ -0,0 +1 @@ >> > >> > +ghc-stage2: ioManagerWakeup: write: Bad file descriptor >> > >> > I don't think these can be caused by my commits, but they should be >> > fixed.... Any offers? >> > >> > Simon >> _______________________________________________ >> ghc-devs mailing list >> [email protected] >> http://www.haskell.org/mailman/listinfo/ghc-devs > > > > _______________________________________________ > ghc-devs mailing list > [email protected] > http://www.haskell.org/mailman/listinfo/ghc-devs >
-- Regards, Austin Seipp, Haskell Consultant Well-Typed LLP, http://www.well-typed.com/ _______________________________________________ ghc-devs mailing list [email protected] http://www.haskell.org/mailman/listinfo/ghc-devs
