So I backed out the path changes. Can we get the 'GHC Build Reports' build bot fixed to publish logs please? I have no idea why nofib is failing as I can view the logs. So can you let me know why its failing but more importantly can we get the log uploads fixed.
I want to make nofib more useful. I've created a ticket to track this here: http://hackage.haskell.org/trac/ghc/ticket/5793 Basically though the recent changes were about cleaning. So removed dead code. And a lot of work to get all the benchmarks from Fibon working. As part of this I created a new top level directory "benchmarks" and put all the benchmarks under it. We now have the following benchmark groups: - imaginary - spectral - real - gc - hackage - parallel - repa - shootout - smp I've left the top 3 on be default as before for now but once I've done some more work would like to enable all of these by default. Cheers, David On 19 January 2012 00:49, Simon Marlow <[email protected]> wrote: > On 18/01/2012 19:16, David Terei wrote: >> >> On 18 January 2012 05:03, Simon Marlow<[email protected]> wrote: >>> >>> On 17/01/2012 19:13, David Terei wrote: >>>> >>>> >>>> Repository : ssh://darcs.haskell.org//srv/darcs/nofib >>>> >>>> On branch : master >>>> >>>> >>>> >>>> http://hackage.haskell.org/trac/ghc/changeset/0449cb065437fc8014b6669e5f1c2c8f4a926d16 >>>> >>>>> --------------------------------------------------------------- >>>> >>>> >>>> >>>> commit 0449cb065437fc8014b6669e5f1c2c8f4a926d16 >>>> Author: David Terei<[email protected]> >>>> Date: Tue Jan 17 10:53:12 2012 -0800 >>>> >>>> Move benchmarks into benchmark/ subdir. >>>> >>> >>> Has there been any discussion of this? You do know we're using nofib >>> quite >>> actively, and this is likely to break scripts etc., right? >>> >> >> No sorry. I wasn't aware of any such things, nofib has always seemed >> quite unmaintained to me but I guess that impression is wrong? Should >> I revert or are the scripts fine. > > > The nofib runs in the nightly builds failed. Could you back this out > please, and then let's discuss what we want to do. > > Cheers, > Simon _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
