Yes, the source is, um, a total mess. /me is glad that he didn't write it.
However, I would rather use an ugly solution that works instead of writing a
custom solution which will take longer to write and debug. I did have to
make a few hacks to the tinderbox source and will make a few more soon, b
Here's a quick module that does just enough to send reports to
Tinderbox. We should be able to drop this module into mktest of
Test::Smoke and have it send reports for each individual config.
http://www.pobox.com/~schwern/src/Devel-Tinderbox-Reporter-0.10.tar.gz
Here's a little example of use.
I just pushed the first version of the perl tinderbox client (1.0p1) to CPAN
and could use some help testing. This may barf in your face, but I would
rather know that now rather than after I make a big announcement about it
and find it doesn't work. I currently have two configs, one for parrot (by
[EMAIL PROTECTED] (Michael G Schwern) writes:
> I've double-checked with the SourceForge guys, we're clear to use
> their machines for smoking Perl.
Do you think you could make them open up for outgoing connections to
the rsync server at cvs.perl.org?
- ask
--
ask bjoern hansen, http://ask.
On Mon, Oct 01, 2001 at 05:10:52PM -0700, Ask Bjoern Hansen wrote:
> [EMAIL PROTECTED] (Michael G Schwern) writes:
> > I've double-checked with the SourceForge guys, we're clear to use
> > their machines for smoking Perl.
>
> Do you think you could make them open up for outgoing connections to
>
sample_config/Tinderconfirg.rsync.pm
^
:)
Hmmm. A lot of this is trying to duplicate what Test::Smoke already
does. Rather than that, I'd suggest working on a generic Tinderbox
interface which we could then plug Test::Smoke into. Basically,
develop generic versions o
On Mon, Oct 01, 2001 at 06:16:01PM -0700, Zach Lipton wrote:
> I just pushed the first version of the perl tinderbox client (1.0p1) to CPAN
Wow, I downloaded the Tinderbox server source. What a disaster! I'm
really dubious about using this for Perl.
What are our other options? Something to
It was somewhat dumb of me not to do enough manual testing on this (this is
why I have to get some automated tests up), but I fixed all the errors and
things should be good to go.
I also fixed an issue on the server side where the logs weren't being
displayed. That should be fixed now. I am curre
