Re: Attempt at a real world benchmark

On 2016-12-09 08:31, Bardur Arantsson wrote: > Actually, now that I think about it: What about if this were integrated > into the Cabal infrastructure? If I specify "upload-perf-numbers: True" > in my .cabal file, any project on (e.g.) GitHub that wanted to opt-in > could do so, they could build

Re: Attempt at a real world benchmark

On 2016-12-08 17:04, Joachim Breitner wrote: > Hi, > > Am Donnerstag, den 08.12.2016, 01:03 -0500 schrieb Joachim Breitner: >> I am not sure how useful this is going to be: >> + Tests lots of common and important real-world libraries. >> − Takes a lot of time to compile, includes CPP macros and

Re: Attempt at a real world benchmark

> On Dec 9, 2016, at 1:00 PM, Joachim Breitner wrote: > > Hi, > > Am Freitag, den 09.12.2016, 09:50 +0800 schrieb Moritz Angermann: >> Hi, >> >> let me thank you perusing this! >> I am not sure how useful this is going to be: + Tests lots of common and

Re: Attempt at a real world benchmark

Hi, let me thank you perusing this! >> I am not sure how useful this is going to be: >> + Tests lots of common and important real-world libraries. >> − Takes a lot of time to compile, includes CPP macros and C code. >> (More details in the README linked above). > > another problem with the

Re: Windows validate failures

Simon Peyton Jones via ghc-devs writes: > I'm getting irreproducible validate failures on Windows. Here's the output: > What commit are you on? The plugins issues I've seen before but I believe the "Errno 17" issues we recently fixed. Cheers, - Ben signature.asc

Linux Harbormaster host

Hello everyone, This morning I noticed that the Linux Harbormaster builder somehow got stuck. I've killed off the hung build and added a timeout to the build script to prevent this from happening again. That being said, it may take a while for it to catch up so don't be surprised if it takes a

Re: Attempt at a real world benchmark

Hi, Am Donnerstag, den 08.12.2016, 01:03 -0500 schrieb Joachim Breitner: > I am not sure how useful this is going to be: >  + Tests lots of common and important real-world libraries. >  − Takes a lot of time to compile, includes CPP macros and C code. > (More details in the README linked above).

RE: Attempt at a real world benchmark

I'm delighted to see all this traffic about GHC perf -- thank you. 277 modules sounds like quite a lot; but in general a test suite that took a while (minutes, not hours) to compile would be fine. We can run it on a nightly server somewhere. Having a dashboard where you can see the results

Windows validate failures

I'm getting irreproducible validate failures on Windows. Here's the output: Unexpected failures: ghci/prog003/prog003.run prog003 [bad exit code] (ghci) plugins/plugins07.run plugins07 [bad exit code] (normal) plugins/T10420.runT10420 [bad exit code] (normal)