[nightly] 06-Nov-2006 build of 6.6 branch on x86_64-unknown-linux (cam-03-unx.europe.corp.microsoft.com)

[Donald Bruce Stewart]

igloo:
> On Tue, Nov 07, 2006 at 10:23:38AM +0000, Simon Marlow wrote:
> > GHC Build Reports wrote:
> > 
> > >Unexpected failures:
> > >   bytestring001(normal,opt,optasm,prof,profasm,ghci,threaded1,threaded2)
> > >   bytestring004(normal,opt,optasm,prof,profasm,ghci,threaded1,threaded2)
> > >   bytestring005(normal,opt,optasm,prof,profasm,ghci,threaded1,threaded2)
> > >
> > >----------------------------------------------------
> > >Nightly run ended at Tue Nov 7 02:34:59 GMT 2006
> > 
> > Anyone know what these bytestring failures on the 6.6 branch are?
> 
> The logs have:
> 
> bytestring004.hs:124:0:
>     Duplicate instance declarations:
>       instance (Arbitrary a) => Arbitrary (Maybe a)
>     -- Defined at bytestring004.hs:124:0
>       instance (Arbitrary a) => Arbitrary (Maybe a)
>     -- Defined in Test.QuickCheck
> 
> so it looks like they're just clashing with the recent addition of
> instances to the (extralibs) QuickCheck. Removing the instances and
> requiring the latest QuickCheck is probably reasonable here - it'll be
> in 6.6.1's extralibs when it's released anyway, and it will Just Work
> for up-to-date darcs builds. I can do that once I have an up-to-date
> build.

Looks like the  new Maybe a instance is clashing. Should be easy to fix.

-- Don