I think my buildbot is working, only it has an error now
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Now I have Ubuntu "Feisty Fawn" PowerPC(G3) using self-built ghc-6.6.1+mtl-1.0 and I forced a build (after manually doing `scons fullclean`). http://www.indiegigs.co.uk:8010/linux_ppc/builds/112/step-yhc/0 scons: *** Source `depends/play/Data/Generics/PlayInternal.hi' not found, needed by target `depends/play/Data/Generics/Play.o'. Stop. scons: building terminated because of errors. Is the buildbot infrastructure surviving? If there are libraries needed but not installed under some ghc versions would it be easy for the build infrastructure to get them if necessary (bytestring; mtl?) (If python>=2.5 do we need to download and build ctypes ourselves, since I think python-2.5 includes it?) Isaac -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGNHzfHgcxvIWYTTURAi1BAJ46Hgv2cGc+UHukYMg6iP6iN5LrogCgh2h0 smkNIf4PnnnRdytRPLeeiU4= =V6SA -----END PGP SIGNATURE-----
Hi Isaac
http://www.indiegigs.co.uk:8010/linux_ppc/builds/112/step-yhc/0 scons: *** Source `depends/play/Data/Generics/PlayInternal.hi' not found, needed by target `depends/play/Data/Generics/Play.o'. Stop. scons: building terminated because of errors.
Fixed, my fault - I changed Play (the library) and didn't update Yhc which relies on the Soncscript.
Is the buildbot infrastructure surviving?
The buildbot infrastructure is fine, the compiler has taken a bit of a knock with moving to new dependencies - because fps vs bytestring requires GHC 6.8 and extensions to .cabal which haven't been written yet to work properly... I'm considering reverting the move to binary, or writing a version-neutral wrapper for the time being. Thanks Neil
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Neil Mitchell wrote:
Fixed, my fault - I changed Play (the library) and didn't update Yhc which relies on the Soncscript.
Is the buildbot infrastructure surviving?
The buildbot infrastructure is fine
it seems that yhc@haskell.org is no longer being spammed with buildbot failures, and my buildbot hasn't started trying again in response to that commit, so I'm a little suspicious -- not that I really understand quite how it's "supposed to" work... Isaac -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGNIZUHgcxvIWYTTURAlLjAKCp6If/lROI198SaE3yKdT0fNhHLgCZAX3V 8JJuTLyCrgsT95ZaegFrja4= =z252 -----END PGP SIGNATURE-----
Hi Isaac
it seems that yhc@haskell.org is no longer being spammed with buildbot failures
This is intentional. We now only send buildbot messages when a bot goes from working -> failing. The idea was to eliminate spamming people, especially if a bot is broken due to missing config changes etc.
and my buildbot hasn't started trying again in response to that commit, so I'm a little suspicious -- not that I really understand quite how it's "supposed to" work...
I've manually kicked off a build on your machine. However, I do think it should have done so automatically by now (it polls every 10 minutes to check if the darcs repo has changed). Andrew: Does buildbot still check for changes? Has some service got turned off or something? Thanks Neil
On 4/29/07, Neil Mitchell
Andrew: Does buildbot still check for changes? Has some service got turned off or something?
It started timing out regularly when downloading the file from darcs.haskell.org that it uses to see if there has been a change. Each time it did that it sent me an email so I turned it off until I got a chance to see why it was failing. Unfortunately I then forgot I'd disabled it. I've turned it on again so we'll see what happens... Andrew
participants (3)
-
Andrew Wilkinson -
Isaac Dupree -
Neil Mitchell