Hi,
Am Sonntag, den 19.03.2017, 21:37 -0400 schrieb Reid Barton:
> > Even if it does, it will take a while to catch up.
>
> Yep, that's why I was eager to get it working again. At least the
> commits where nofib was broken build a bit faster :)
if you look at
On Sun, Mar 19, 2017 at 2:16 PM, Joachim Breitner
wrote:
> Hi,
>
> Am Sonntag, den 19.03.2017, 13:23 -0400 schrieb Reid Barton:
>> ght? On Sat, Mar 18, 2017 at 1:05 PM, Joachim Breitner
>> > wrote:
>> > Hi,
>> >
>> > correct. It seems that
ght? On Sat, Mar 18, 2017 at 1:05 PM, Joachim Breitner
wrote:
> Hi,
>
> correct. It seems that 'make boot' tries to compile all of nofib, even
> those that are not to be run. So this ought to be revised.
This appears to not actually be the case though, from local
Hi,
correct. It seems that 'make boot' tries to compile all of nofib, even
those that are not to be run. So this ought to be revised.
Greetings,
Joachim
Am Samstag, den 18.03.2017, 01:56 -0400 schrieb Reid Barton:
> Don't know whether it is the same issue, but perf.haskell.org seems
> to
>
Don't know whether it is the same issue, but perf.haskell.org seems to
still have not built anything for the past 3 days, according to
https://github.com/nomeata/ghc-speed-logs/commits/master.
Regards,
Reid Barton
On Wed, Mar 15, 2017 at 5:49 PM, Ben Gamari wrote:
>
Joachim Breitner writes:
> Hi,
>
> a recent change to nofib
> (https://phabricator.haskell.org/rNOFIB313812d319e009d698bc1a4d2e8ac26d4dfe3c0a)
> broke the perf.haskell.org builder, so we won’t be getting perf
> warnings until that is fixed.
>
I've pushed the michalt's
Hi,
a recent change to nofib
(https://phabricator.haskell.org/rNOFIB313812d319e009d698bc1a4d2e8ac26d4dfe3c0a)
broke the perf.haskell.org builder, so we won’t be getting perf
warnings until that is fixed.
I hope that once its up we will not be faced with a large number of
performance changes that