public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: Marco Atzeri <marco.atzeri@gmail.com>
Cc: cygwin-apps@cygwin.com
Subject: Re: python fails asyncio tests (py 3.7 & 3.8)
Date: Mon, 28 Dec 2020 16:08:53 -0800 (PST)	[thread overview]
Message-ID: <Pine.BSF.4.63.2012281557220.35383@m0.truegem.net> (raw)
In-Reply-To: <b7d38149-51df-f430-b0e3-f81052ba38aa@gmail.com>

Hi Marco,

On Mon, 28 Dec 2020, Marco Atzeri via Cygwin-apps wrote:
> On 17.12.2020 10:20, Mark Geisert wrote:
>> Hi Marco,
>> Below is the patch I developed to work around the problem report in
>> https://cygwin.com/pipermail/cygwin/2020-November/246830.html
>> I called the patch file 3.8.3-peercred-cygwin.patch.
>> 
>> I am unable to test the patch myself because of continuing problems 
>> building a new Python.  I don't know if my issues are due to being on 
>> latest Cygwin code vs 3.1.7, or gcc 10.2 vs 9.3, or what.  Could you tell 
>> me what your build environment is like?  I'll try to duplicate it.
>> 
>> Test the patch by running a Python built with it on the example from the 
>> OP. Without the patch, the run would hang in the middle of the test 
>> script.  With the patch, it should quickly complete with 4 unrelated 
>> errors mentioning MSG_OOB.
>> Thanks & Regards,
>> 
>> ..mark
>> 
>
> Hi Mark,
> is this the expected result ?
>
> test_connection_attributes (__main__.TestAPI_UseUnixSocketsPoll) ... ERROR
> /usr/lib/python3.8/unittest/case.py:704: ResourceWarning: unclosed 
> <socket.socket fd=5, family=AddressFamily.AF_UNIX, 
> type=SocketKind.SOCK_STREAM, proto=0>
>  outcome.errors.clear()
>
> It does not freeze

That's a new error to me; I haven't run that test.  I could have been more 
specific in my test instructions.  There are apparently two test series 
(which is also news to me).  They are /usr/lib/python3.8/test and 
.../unittest.  It seems you were in the latter?  The script to run is in 
.../test.  Here's how:
     cd /usr/lib/python3.8/test
     python3.8 test_asyncore.py -v

Separately, I'm still wrestling with build issues.  Just as a known-good 
alternative, how is your test environment set up?  Is your cygwin1.dll 
from standard 3.1.7, or a snapshot, or do you build from git master?  Are 
you using the latest binutils and gcc-g++ packages or something newer?

Thanks for any info you can provide.  I seem to be having issues with 
linking programs having many object files.  Like any Python 3, or the 
Flint math library for examples.  The link fails with a SIGSEGV or an 
assertion failure in cofflink.c.  Nobody else has reported these.
Thanks & Regards,

..mark

  reply	other threads:[~2020-12-29  0:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17  9:20 Mark Geisert
2020-12-28 21:57 ` Marco Atzeri
2020-12-29  0:08   ` Mark Geisert [this message]
2020-12-29  5:41     ` Marco Atzeri
2020-12-29  6:20       ` Marco Atzeri

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=Pine.BSF.4.63.2012281557220.35383@m0.truegem.net \
    --to=mark@maxrnd.com \
    --cc=cygwin-apps@cygwin.com \
    --cc=marco.atzeri@gmail.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).