On 02/08/07, Jan Dubois <[EMAIL PROTECTED]> wrote:
> On Wed, 01 Aug 2007, Robert May wrote:
> > On 31/07/07, Robert May <[EMAIL PROTECTED]> wrote:
> > > I'll post another version as soon as I've shown that it tests clean
> > > (hopefully tomorrow).
>
> I don't quite get the list of test failures.  Are you getting test failures
> from just compiling the ActivePerl sources with `nmake && nmake test`?

Yes.  VC6 (although using the .h files from a more recent SDK).
Win2k.  I don't build perl from source very often, but I don't think
I've ever had a completely clean test run with either ActivePerl or
the 'official' source.

If you're interested I'll do a clean build from the 819 source
tomorrow, and let you see the relevant bits of the test output.

> That would be wrong.  Running without test failures is a prerequisite
> for the releases.

OK - I'll investigate further too, but probably not until the weekend.

> > Attached patches implement the same functionality against AS build 819
> > and, probably more importantly, perl 9.5.9.
> >
> > Tests run without failures (well, the same failures as I get without
> > the patch - see below).

> I'll take a look at your patches once I get a little more time. I may not
> get around to it until the weekend though.

No rush from my perspective.

> Unfortunately we just missed ActivePerl 822, which was already approved
> by QA this afternoon (there is no 821, except on HP-UX).

I've not even caught up with 820 yet!

Thanks for your input.
Rob.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Perl-Win32-GUI-Users mailing list
Perl-Win32-GUI-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/perl-win32-gui-users
http://perl-win32-gui.sourceforge.net/

Reply via email to