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

asyncio pgo + lto buildbot failure: altered environment #97535

Closed
sobolevn opened this issue Sep 25, 2022 · 3 comments
Closed

asyncio pgo + lto buildbot failure: altered environment #97535

sobolevn opened this issue Sep 25, 2022 · 3 comments
Labels
topic-asyncio type-bug An unexpected behavior, bug, or error

Comments

@sobolevn
Copy link
Member

There's a new buildbot failure: https://buildbot.python.org/all/#builders/244/builds/3091

== Tests result: ENV CHANGED ==
414 tests OK.
10 slowest tests:
- test_tools: 3 min 18 sec
- test_concurrent_futures: 2 min 29 sec
- test_multiprocessing_spawn: 2 min
- test_multiprocessing_forkserver: 1 min 38 sec
- test_unparse: 1 min 24 sec
- test_asyncio: 1 min 10 sec
- test_multiprocessing_fork: 1 min 8 sec
- test_tokenize: 1 min 8 sec
- test_unicodedata: 56.2 sec
- test_signal: 48.6 sec
1 test altered the execution environment:
    test_asyncio
22 tests skipped:
    test_devpoll test_gdb test_idle test_ioctl test_kqueue
    test_launcher test_msilib test_perf_profiler test_smtpnet test_ssl
    test_startfile test_tcl test_tix test_tkinter test_ttk
    test_ttk_textonly test_turtle test_winconsoleio test_winreg
    test_winsound test_wmi test_zipfile64
Total duration: 6 min 22 sec
Tests result: ENV CHANGED
make: *** [buildbottest] Error 3
program finished with exit code 2
elapsedTime=383.679571
@sobolevn sobolevn added type-bug An unexpected behavior, bug, or error topic-asyncio labels Sep 25, 2022
@ezio-melotti ezio-melotti moved this to Todo in asyncio Sep 25, 2022
@kumaraditya303
Copy link
Contributor

Subsequent two builds have passed https://buildbot.python.org/all/#/builders/244/builds/3093 so I assume it was just a random flaky failure. Feel free to reopen if this happens again.

@kumaraditya303 kumaraditya303 closed this as not planned Won't fix, can't repro, duplicate, stale Sep 25, 2022
Repository owner moved this from Todo to Done in asyncio Sep 25, 2022
@gvanrossum
Copy link
Member

Maybe we should create a new issue to try and find and fix the reasons why test_asyncio is so flaky? I've run into this many times.

@sobolevn
Copy link
Member Author

Will do!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic-asyncio type-bug An unexpected behavior, bug, or error
Projects
Status: Done
Development

No branches or pull requests

3 participants