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

Test failure on slow processors? #128

Open
davesteele opened this issue Jan 26, 2022 · 3 comments
Open

Test failure on slow processors? #128

davesteele opened this issue Jan 26, 2022 · 3 comments

Comments

@davesteele
Copy link
Contributor

Unit tests have failed on ppc64el hardware:

https://ci.debian.net/data/autopkgtest/unstable/ppc64el/a/aiofiles/18419050/log.gz

autopkgtest [08:17:49]: test unittests.py: [-----------------------
============================= test session starts ==============================
platform linux -- Python 3.9.10, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
rootdir: /tmp/autopkgtest-lxc.9mzzz2i1/downtmp/build.Jix/src
plugins: asyncio-0.16.0
collected 155 items

tests/test_os.py ......                                                  [  3%]
tests/test_simple.py ..                                                  [  5%]
tests/threadpool/test_binary.py ........................................ [ 30%]
...........................................................              [ 69%]
tests/threadpool/test_concurrency.py .                                   [ 69%]
tests/threadpool/test_open.py ...                                        [ 71%]
tests/threadpool/test_text.py .......................................... [ 98%]
..                                                                       [100%]

============================= 155 passed in 1.76s ==============================
Task was destroyed but it is pending!
task: <Task pending name='Task-123' coro=<test_slow_file.<locals>.serve_file() running at /tmp/autopkgtest-lxc.9mzzz2i1/downtmp    /build.Jix/src/tests/threadpool/test_concurrency.py:37> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at     /usr/lib/python3.9/asyncio/futures.py:384, <TaskWakeupMethWrapper object at 0x7fff84d62070>()]>>
autopkgtest [08:17:51]: test unittests.py: -----------------------]
autopkgtest [08:17:52]: test unittests.py:  - - - - - - - - - - results - - - - - - - - - -
unittests.py         FAIL stderr: Task was destroyed but it is pending!
autopkgtest [08:17:52]: test unittests.py:  - - - - - - - - - - stderr - - - - - - - - - -
Task was destroyed but it is pending!
task: <Task pending name='Task-123' coro=<test_slow_file.<locals>.serve_file() running at /tmp/autopkgtest-lxc.9mzzz2i1/downtmp    /build.Jix/src/tests/threadpool/test_concurrency.py:37> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.9/asyncio/futures.py:384, <TaskWakeupMethWrapper object at 0x7fff84d62070>()]>>

Does test_slow_file() need to verify serve_file() is drained before cleaning up?

@davesteele
Copy link
Contributor Author

This has come up before. See 995bbea

davesteele added a commit to davesteele/aiofiles that referenced this issue Jan 26, 2022
It has been unreliable in the past (995bbea), and is now failing for
the Debian ppc64el architecture. Submitted upstream
(Tinche#128) and disable for
autopkgtest.
@Tinche
Copy link
Owner

Tinche commented Jan 26, 2022

We used to have ppc64e tests back on Travis, but I don't think GitHub supports them.

Anyway, looks like the tests pass but there's some stderr output that's unexpected?

@davesteele
Copy link
Contributor Author

Looks like another race.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants