RE: [commit: ghc] master: Adjust test suite stats (a055f24)

Ha! They didn’t regress for me. I validated before committing. How strange. I agree about keeping it green Simon From: ghc-devs [mailto:ghc-devs-boun...@haskell.org] On Behalf Of David Feuer Sent: 28 August 2017 22:13 To: ghc-devs Subject: RE: [commit: ghc] master:

RE: [commit: ghc] master: Adjust test suite stats (a055f24)

These were regressions from your simplifier refactoring. Yes, we should investigate. I'll open a ticket this evening, unless someone else gets to it first. But we surely don't want to keep CI red on every commit until then. David FeuerWell-Typed, LLP Original message From:

RE: [commit: ghc] master: Adjust test suite stats (a055f24)

David, are you sure we want to accept a more than 5% increase in compile time without investigation? What commit caused these increases? Maybe they are readily squashed? Generally we are trying to improve compiler perf not accept it getting worse! Simon | -Original Message- | From:

Re: Alex install failure

On Mon, Aug 28, 2017 at 1:42 PM, Ben Gamari wrote: > Hmm, interesting. So it seems almost certain at this point that you are > not running the lock daemon. In contrast, on an NFSv3 client that I > setup I see, > This is moderately likely to be common: many people

RE: Alex install failure

Ben Gamari writes: snip > Hmmm. I'll need to do some reading at this point. > I am now able to reproduce the issue locally. Stay tuned. signature.asc Description: PGP signature ___ ghc-devs mailing list ghc-devs@haskell.org

RE: Alex install failure

Simon Peyton Jones writes: > sudo rpcinfo -p >program vers proto port service > 104 tcp111 portmapper > 103 tcp111 portmapper > 102 tcp111 portmapper > 104 udp111 portmapper > 10

RE: Alex install failure

sudo rpcinfo -p program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111

RE: Alex install failure

Simon Peyton Jones via ghc-devs writes: > | note that you mistyped "lockd" (aka "lock daemon") as "locd" > > Oh, sorry about mistyping > > simonpj@cam-05-unx:~/tmp$ ps -Af | grep lockd > root 140 2 0 2016 ?00:00:00 [kblockd] > simonpj 7882 1184 0

RE: Alex install failure

| note that you mistyped "lockd" (aka "lock daemon") as "locd" Oh, sorry about mistyping simonpj@cam-05-unx:~/tmp$ ps -Af | grep lockd root 140 2 0 2016 ?00:00:00 [kblockd] simonpj 7882 1184 0 13:22 pts/700:00:00 grep lockd | also, the output of "rpcinfo -p" would