From: Marco Atzeri <marco.atzeri@gmail.com>
To: Mark Geisert <mark@maxrnd.com>
Cc: cygwin-apps@cygwin.com
Subject: Re: Test failures from 'cygport python39.cygport test' etc
Date: Wed, 8 Mar 2023 21:29:49 +0100 [thread overview]
Message-ID: <8bf0e282-23a8-f0a4-41f6-3332190bbbd7@gmail.com> (raw)
In-Reply-To: <CAB8Xom8VRupB8VppX6-60aRbtae3eL=x4u05bWXnpALUxiEQbw@mail.gmail.com>
On 28.02.2023 12:56, marco atzeri wrote:
> On Tue, Feb 28, 2023 at 7:09 AM Mark Geisert via Cygwin-apps wrote:
>>
>> Hi Marco,
>> I'm seeing test failures and hangs on the 'cygport test' step for both
>> Python 3.9 and 3.8. 3.9 has 37 failures out of 423 tests, 3.8 has 39
>> failures out of 425 tests. Both releases have 3 tests hanging after as
>> much as 20 minutes wait w/no cputime: test_asyncio, test_ssl, test_io.
>>
>> My procedure is to (with cygport) prep, build, test. Do I need to
>> 'install' before 'test'? I believe I tried that but it made no
>> difference. Is there a different procedure you use to test the Python
>> builds?
>> Thanks & Regards,
>>
>> ..mark
>
> For what I remember some tests always hanged. Also in previous releases
Hi Mark,
just built the 3.9.16, I will deploy shortly
the test stacked are:
0:26:57 load avg: 0.59 running: test_io (15 min 55 sec), test_asyncio
(26 min 49 sec), test_ssl (23 min 2 sec)
In addition just to have an order of magnitude:
$ grep failed python39-3.9.16-1-check.log | wc -l
53
$ grep passed python39-3.9.16-1-check.log | wc -l
371
Regards
Marco
prev parent reply other threads:[~2023-03-08 20:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 6:09 Mark Geisert
2023-02-28 11:56 ` marco atzeri
2023-03-08 20:29 ` Marco Atzeri [this message]
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=8bf0e282-23a8-f0a4-41f6-3332190bbbd7@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
--cc=mark@maxrnd.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).