Test failures from 'cygport python39.cygport test' etc

Test failures from 'cygport python39.cygport test' etc

[Mark Geisert]

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

Re: Test failures from 'cygport python39.cygport test' etc

[marco atzeri]

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

Re: Test failures from 'cygport python39.cygport test' etc

[Marco Atzeri]

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