This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Asyncio test fails under Win 7
Type: behavior Stage: resolved
Components: asyncio, Build, Windows Versions: Python 3.8
Status: closed Resolution: duplicate
Dependencies: Superseder: [Windows] : Proactor test_sendfile_close_peer_in_the_middle_of_receiving failure
View: 41682
Assigned To: Nosy List: asvetlov, iritkatriel, pansen, paul.moore, steve.dower, tim.golden, vstinner, xtreak, yselivanov, zach.ware
Priority: normal Keywords:

Created on 2018-07-28 12:58 by pansen, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Messages (5)
msg322558 - (view) Author: Wöllert (pansen) * Date: 2018-07-28 12:58
When running tests I encounter the following error for the test:

test_sock_sendfile_not_regular_file (test.test_asyncio.test_proactor_events.ProactorEventLoopUnixSockSendfileTests)

Microsoft Visual C++ Runtime Library
Debug Assertion Failed!

Program: ...\EP2018\cpython\PCbuild\win32\python_d.exe
File: minkernel\crts\ucrt\src\appcrt\lowio\osfinfo.cpp
Line: 257

Expression: fh >= 0 && (unsigned)fh < (unsigned)_nhandle


However, when ignoring the MSCR error, the tests succeed without failing.

In addition the following failed (but not consistently):

FAIL: test_sendfile_close_peer_in_the_middle_of_receiving (test.test_asyncio.test_events.ProactorEventLoopTests)
Traceback (most recent call last):
  File "C:\Users\woellert\Desktop\EP2018\cpython\lib\test\test_asyncio\", line 2510, in test_sendfile_close_peer_in_the_middle_of_receiving
AssertionError: False is not true : 131072


Specs: Windows 7 SP1 64bit, 

- Cloned master from github
- Installed Visual Studio 2017 Community
- Compiled with `PCbuild\build.bat -e -d` (also used 64bit via -p x64)
- Ran tests with `python.bat -m test.test_asyncio -v`
msg322563 - (view) Author: Wöllert (pansen) * Date: 2018-07-28 14:27
Regarding the MVSC runtime message, there is an issue already here:
msg326476 - (view) Author: Karthikeyan Singaravelan (xtreak) * (Python committer) Date: 2018-09-26 15:26
ProactorEventLoop is the default event loop with issue34687. There doesn't seem to be any warnings in buildbots as I have checked and as @panesen has mentioned this is not consistent. I am adding Victor as a notification if he has any thoughts. Victor, feel free to remove yourself if this is not relevant.

msg401282 - (view) Author: Irit Katriel (iritkatriel) * (Python committer) Date: 2021-09-07 14:13
Changing type since the crash was fixed under issue23919.

There remains (possibly) the failure of test_sendfile_close_peer_in_the_middle_of_receiving.
msg401304 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2021-09-07 16:39
test_sendfile_close_peer_in_the_middle_of_receiving() failure is tracked by bpo-41682.
Date User Action Args
2022-04-11 14:59:04adminsetgithub: 78443
2021-09-07 16:41:26iritkatrielsetstatus: open -> closed
superseder: [Windows] : Proactor test_sendfile_close_peer_in_the_middle_of_receiving failure
resolution: duplicate
stage: resolved
2021-09-07 16:39:23vstinnersetmessages: + msg401304
2021-09-07 14:13:55iritkatrielsettype: crash -> behavior

messages: + msg401282
nosy: + iritkatriel
2018-09-26 15:27:04xtreaksetnosy: + vstinner
2018-09-26 15:26:44xtreaksetmessages: + msg326476
2018-09-26 12:47:42xtreaksetnosy: + xtreak
2018-07-28 14:27:26pansensetmessages: + msg322563
2018-07-28 12:58:41pansencreate