On Oct 2, 2008, at 4:21 PM, James Turnbull wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Luke Kanies wrote: >> James has been working on it, but I guess he's too busy galivanting >> around the world to finish it up. :) > > It's almost ready - the major hold-up is that too many bloody tests > fail > right now for dump reasons that any actual failing tests resulting for > commits slip through the cracks. So fix some test - hint hint - and > we > can get it going. :)
Hey, we're doing what we can on the tests. Considering I've got two babies duct-taped to my chest, I think I'm doing pretty well. :P > >> I (and many others) completely agree that a buildbot is the right >> answer. > > Ditto. > >>> I don't really see a big problem with having say different test >>> targets that call what you want, just default to sensible behaviour. >>> As every developer can't reasonably be expected to have every os >>> locally available having a good visible feedback cycle for >>> integration >>> tests would be really useful. >> >> Okay. I'll open a ticket now. I'll plan on creating an >> 'integration_tests' rake task, along with an 'all_tests' task, I >> guess. > > +1 > > n tests? >>> You already have a dir structure split so it's just wiring the >>> Rakefile and autotest config differently and setting up an >>> environment >>> for integration tests. >> >> Yeah. >> > > +1 -- Wear the old coat and buy the new book. -- Austin Phelps --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en -~----------~----~----~----~------~----~------~--~---
