Mon Feb 1 23:24:05 PST 2010 simo...@microsoft.com
* Test Trac #3831: SpecConstr blowup
A ./tests/ghc-regress/simplCore/should_compile/T3831.hs
M ./tests/ghc-regress/simplCore/should_compile/all.T +1
View patch online:
http://darcs.haskell.org/testsuite/_darcs/patches/20100202072405-12
Sun Jan 31 16:24:20 PST 2010 simo...@microsoft.com
* Fix Trac #3831: blowup in SpecConstr
It turned out that there were two bugs. First, we were getting an
exponential number of specialisations when we had a deep nest of
join points. See Note [Avoiding exponential blowup]. I fixed thi
Build description = HEAD on i386-unknown-linux
(cam-02-unx.europe.corp.microsoft.com)
Build location= /playpen/simonmar/nightly/HEAD
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx
Nightly build started on cam-02-unx at Mon Feb 1 18:00:01 GMT 2010.
checking out
On 01/02/2010, at 22:19 , Simon Marlow wrote:
> Correct me if I'm wrong, but your buildbot runs entirely on the client and is
> designed to do a (configurable) build and email the results, right?
Yes, that's all -- it's just something that I hacked together. The potential to
use Ian's new buil
Build description = HEAD on x86_64-unknown-linux
(cam-04-unx.europe.corp.microsoft.com)
Build location= /64playpen/simonmar/nightly/HEAD-cam-04-unx
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-04-unx
Nightly build started on cam-04-unx at Mon Feb 1 19:00:01 GMT 2010.
***
On 01/02/2010 06:41, Ben Lippmeier wrote:
On 30/01/2010, at 3:58 , Neil Mitchell wrote:
I've got buildbot running reasonably reliably, but writing
configuration files in Python is a little annoying as I don't really
know what I'm doing. If you were to make your version of buildbot
decoupled fr
