From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: perl-5.18.2-1 (x86) [test] Attn Maintainers with perl reqs
Date: Sun, 04 May 2014 12:56:00 -0000 [thread overview]
Message-ID: <53663901.1010204@tiscali.co.uk> (raw)
In-Reply-To: <87ha5658ix.fsf@Rainer.invalid>
On 04/05/14 08:04, Achim Gratz wrote:
> David Stacey writes:
>> I've built perl-Text-CSV_XS-1.07 for perl-5.18.2 on 32-bit
>> Cygwin. Functionally, everything seems OK. However, the performance of
>> the test harness was quite poor. With perl-5.14.2, the
>> perl-Text-CSV_XS test harness rattled through in 8 seconds; with
>> perl-5.18.2 it was 68 seconds (same PC) - that's over 8x slower. Is
>> this something you were expecting?
> Yes, if you set TEST_VERBOSE=1 you'll see that with the old Perl you've
> skipped some 20000 tests with the message "Encode is too old for these
> tests", which is no longer the case. Skipping these tests with the new
> Perl gets the test times back to where they were, if not slightly
> faster.
Thanks for explaining - I hadn't spotted that because the number of
tests reported was the same for both versions of perl. I'll do some more
testing and upload a test version in the next day or so.
Dave.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-05-04 12:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 23:12 Reini Urban
2014-05-01 21:32 ` David Stacey
2014-05-04 7:08 ` Achim Gratz
2014-05-04 12:56 ` David Stacey [this message]
2014-05-02 8:32 ` Achim Gratz
2014-05-29 18:27 ` Reini Urban
2014-05-29 21:17 ` Achim Gratz
2014-05-30 21:02 ` Yaakov (Cygwin/X)
2014-05-31 0:29 ` David Stacey
2014-05-05 12:55 ` David Stacey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53663901.1010204@tiscali.co.uk \
--to=drstacey@tiscali.co.uk \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).