Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

test_asyncio fails always #74075

Closed
ThomasKnox mannequin opened this issue Mar 23, 2017 · 8 comments
Closed

test_asyncio fails always #74075

ThomasKnox mannequin opened this issue Mar 23, 2017 · 8 comments
Labels
topic-asyncio

Comments

@ThomasKnox
Copy link
Mannequin

ThomasKnox mannequin commented Mar 23, 2017

BPO 29889
Nosy @vstinner, @ned-deily, @asvetlov, @zware, @1st1, @zhangyangyu, @torsava

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2017-12-20.20:51:31.338>
created_at = <Date 2017-03-23.21:30:44.217>
labels = ['expert-asyncio']
title = 'test_asyncio fails always'
updated_at = <Date 2017-12-20.20:51:31.336>
user = 'https://bugs.python.org/ThomasKnox'

bugs.python.org fields:

activity = <Date 2017-12-20.20:51:31.336>
actor = 'asvetlov'
assignee = 'none'
closed = True
closed_date = <Date 2017-12-20.20:51:31.338>
closer = 'asvetlov'
components = ['asyncio']
creation = <Date 2017-03-23.21:30:44.217>
creator = 'Thomas Knox'
dependencies = []
files = []
hgrepos = []
issue_num = 29889
keywords = []
message_count = 8.0
messages = ['290059', '290060', '290066', '290067', '290068', '290075', '293335', '308812']
nosy_count = 8.0
nosy_names = ['vstinner', 'ned.deily', 'asvetlov', 'zach.ware', 'yselivanov', 'xiang.zhang', 'torsava', 'Thomas Knox']
pr_nums = []
priority = 'normal'
resolution = 'works for me'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue29889'
versions = ['Python 3.6']
@ThomasKnox
Copy link
Mannequin Author

ThomasKnox mannequin commented Mar 23, 2017

Downloaded Python 3.6.1 source code onto CentOS 7.3 (64 bit), Fedora 25 (64 bit), Ubuntu 16.10 (64 bit) and Raspberry Pi 8.0 (32 bit).

Configured with
./configure --enable-shared --enable-optimizations --enable-loadable-sqlite-extensions --disable-ipv6 --with-system-expat --with-system-ffi --with-threads

On every platform, when running the profile generation code, test_asyncio fails with this error message:

0:06:45 [ 25/405] test_asyncio
Executing <Task finished coro=<CoroutineTests.test_async_def_wrapped.<locals>.start() done, defined at /home/pi/Source/Python-3.6.1/Lib/test/test_asyncio/test_pep492.py:150> result=None created at /home/pi/Source/Python-3.6.1/Lib/asyncio/base_events.py:446> took 2.106 seconds
0:13:11 [ 26/405] test_asyncore -- test_asyncio failed in 6 min 27 sec

@ThomasKnox ThomasKnox mannequin added build The build process and cross-build tests Tests in the Lib/test dir labels Mar 23, 2017
@ned-deily
Copy link
Member

There have been other reports (e.g. bpo-29712) of failures when using --enable-optimizations with --enable-shared. Can you see if removing --enable-shared makes a difference for your configurations?

@ned-deily ned-deily added topic-asyncio and removed tests Tests in the Lib/test dir build The build process and cross-build labels Mar 23, 2017
@ThomasKnox
Copy link
Mannequin Author

ThomasKnox mannequin commented Mar 23, 2017

I changed the configuration flags to be:

pi@pi3:~/Source/Python-3.6.1 $ ./configure --enable-optimizations --enable-loadable-sqlite-extensions --disable-ipv6 --with-system-expat --with-system-ffi --with-threads

The profiling filed again with:

0:04:47 [ 25/405] test_asyncio
Executing <Task finished coro=<CoroutineTests.test_async_def_wrapped.<locals>.start() done, defined at /home/pi/Source/Python-3.6.1/Lib/test/test_asyncio/test_pep492.py:150> result=None created at /home/pi/Source/Python-3.6.1/Lib/asyncio/base_events.py:446> took 1.187 seconds
0:08:45 [ 26/405] test_asyncore -- test_asyncio failed in 3 min 59 sec

But at least it failed 2.5 minutes faster. :)

@zware
Copy link
Member

zware commented Mar 23, 2017

Does the build fail, or just the test in the profile generation?

@ThomasKnox
Copy link
Mannequin Author

ThomasKnox mannequin commented Mar 23, 2017

The build succeeds, but the profile generation fails (only the test_asyncio portion fails), then does a new profiled build after the profiling run completes which succeeds.

Then, when doing a 'make install', it builds the entire thing again and runs another profile generation run which also fails, then a new profiled build. Possibly because the first profile run failed?

On an RPi, this is exceedingly painful as a build/profile/build cycle takes about 10 hours. So doing it twice is double-unfun.

@zhangyangyu
Copy link
Member

Then, when doing a 'make install', it builds the entire thing again and runs another profile generation run which also fails, then a new profiled build. Possibly because the first profile run failed?

This is a known issue. Some build commands always clear the environment and rebuild. See bpo-29243.

@vstinner
Copy link
Member

vstinner commented May 9, 2017

Can someone test again with a development branch? The bpo-29243 has been fixed in 2.7, 3.5, 3.6 and master (3.7) branches thanks to Tomas Orsava!

@asvetlov
Copy link
Contributor

Confirm: no problems on master (Ubuntu 17.10).

Closing the issue.

@ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
topic-asyncio
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@vstinner @asvetlov @zhangyangyu @ned-deily @zware