On Mar-26, Dan Sugalski wrote: > The VS/.NET build works fine, though three of the tests fail for odd > reasons. Those look like potential test harness errors. > > The cygwin build sorta kinda works OK, but the link fails because of > a missing _inet_pton. I seem to remember this cropping up in the past > and I thought we'd gotten it fixed, but apparently not. > > Anyway, these are set for hourly builds at half-hour offsets, so if > you check in any significant changes it'd be advisable to take a look > at the results. For those that don't know, all the tinderbox info is > web-accessable at > http://tinderbox.perl.org/tinderbox/bdshowbuild.cgi?tree=parrot
A couple of weeks back, I also beefed up the error parsing stuff a bit on my Parrot tinderbox summarizer at http://foxglove.dnsalias.org/parrot/ so that it should give a good "what's broken and why" summary at a glance. Note that because I only run the summarizer once an hour at 17 minutes past the hour, it is not the right place to go if you're watching to see if your commit broke anything. For that, see the official URL above.
