public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Christensen <dpchrist@holgerdanske.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin Perl has slowed in recent months
Date: Sun, 22 May 2022 12:11:05 -0700	[thread overview]
Message-ID: <b4ea7bca-242a-4c9c-6736-ec997f6d6877@holgerdanske.com> (raw)
In-Reply-To: <69f7b5b2-0730-bce2-90d8-95a7fde0a15f@t-online.de>

On 5/21/22 10:55, Hans-Bernhard Bröker wrote:
> Am 18.05.2022 um 03:53 schrieb David Christensen:
> 
>  > I am working on a Perl module that runs on various Unix-like platforms.
>  > When I 'make test' on similar computers:
>  >
>  > FreeBSD 12.3-RELEASE         28 wallclock secs
>  > Debian GNU/Linux 11.3          31 wallclock secs
>  > macOS 11.6.2              36 wallclock secs
>  > Windows 7 / Cygwin 3.3.5-1    509 wallclock secs
> 
> Given the complete lack of information about what that Perl module of 
> yours might be doing, that's hard to have a meaningful discussion about.


Thank you for the response.  I was hoping there was a known issue. 
Apparently, not.


The above module is proprietary, so I thought I would profile some 
similar CPAN modules to generate discussion information:

2022-05-22 01:25:39 dpchrist@dht4s3r1 ~
$ systeminfo | egrep '^OS (Name|Version)' ; uname -a ; cygcheck -c cygwin
OS Name:                   Microsoft Windows 7 Professional
OS Version:                6.1.7601 Service Pack 1 Build 7601
CYGWIN_NT-6.1-7601 dht4s3r1 3.3.5-341.x86_64 2022-05-13 12:27 UTC x86_64 
Cygwin
Cygwin Package Information
Package              Version        Status
cygwin               3.3.5-1        OK

2022-05-22 01:26:45 dpchrist@dht4s3r1 ~
$ cpan install Devel::NYTProf
<snip>
t/50-errno.t ............. 1/8
#   Failed test '$! should not be altered by NYTProf i/o'
#   at t/50-errno.t line 58.
#          got: '0'
#     expected: '3'
# Looks like you failed 1 test of 8.
t/50-errno.t ............. Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/8 subtests
<snip>
Test Summary Report
-------------------
t/50-errno.t           (Wstat: 256 Tests: 8 Failed: 1)
   Failed test:  6
   Non-zero exit status: 1
Files=55, Tests=4736, 570 wallclock secs ( 0.64 usr  1.06 sys + 104.19 
cusr 403.73 csys = 509.62 CPU)
Result: FAIL
Failed 1/55 test programs. 1/4736 subtests failed.
make: *** [Makefile:1284: test_dynamic] Error 255
   JKEENAN/Devel-NYTProf-6.11.tar.gz
   /usr/bin/make test -- NOT OK
//hint// to see the cpan-testers results for installing this module, try:
   reports JKEENAN/Devel-NYTProf-6.11.tar.gz


STFW:

https://github.com/Perl/perl5/issues/12389


Any suggestions?

David

  reply	other threads:[~2022-05-22 19:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18  1:53 David Christensen
2022-05-21 17:55 ` Hans-Bernhard Bröker
2022-05-22 19:11   ` David Christensen [this message]
2022-05-23 18:47     ` Lee
2022-05-23 21:22       ` David Christensen
2022-05-24  8:25       ` Csaba Raduly
2022-05-24  8:47         ` Sam Edge
2022-05-24 15:03           ` David Christensen
2022-05-24 15:59             ` Sam Edge
2022-05-24 17:09               ` David Christensen
2022-05-24 19:31             ` Brian Inglis
2022-05-24 18:57 ` Achim Gratz
2022-05-25  6:36 ` David Christensen
2022-05-25 15:04   ` gs-cygwin.com
2022-05-25 20:06     ` David Christensen

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=b4ea7bca-242a-4c9c-6736-ec997f6d6877@holgerdanske.com \
    --to=dpchrist@holgerdanske.com \
    --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).