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 fails on ppc64le #2280

Closed
lgbaldoni opened this issue Sep 20, 2017 · 9 comments
Closed

Test fails on ppc64le #2280

lgbaldoni opened this issue Sep 20, 2017 · 9 comments

Comments

@lgbaldoni
Copy link

Could this be an endianness problem?

aiohttp_test.txt

@fafhrd91
Copy link
Member

it is very hard to debug problem without access to hardware :)
could you run tests with -v,
tests/test_web_protocol.py:791 seems aiohttp problem

but second looks like asyncio problem, could you run asyncio tests suit?

@lgbaldoni
Copy link
Author

lgbaldoni commented Sep 20, 2017

Here's the log for the tests in verbose mode:
aiohttp_test_v.txt

I'm encountering some difficulty in running tests for sphinxcontrib-asyncio, but please let me know if it's really important.

Also this problem appears to be intermittent. It fails 1 out of 4 times.

The only thing out of the ordinary in sphinxcontrib-asyncio is that my distro (openSUSE) supplies a separate __init__.py in sphinxcontrib to avoid a namespace clash, but I'm not sure this is a factor.

@fafhrd91
Copy link
Member

I am afraid, without access to hardware I can not help. especially for transient errors.

@lgbaldoni
Copy link
Author

That's unfortunate. I suppose I'll have to exclude the build for that target.

By the way, I couldn't find any test to run in the sphinxcontrib-asyncio tarball.

@asvetlov
Copy link
Member

It is a very simple sphinx markup plugin, tests are not required.

@lgbaldoni
Copy link
Author

@asvetlov
so you'd rule out the problem coming from there?

@asvetlov
Copy link
Member

sphinxcontrib-asyncio is needed for docs generation only.
aiohttp test failure on ppc is not related to it.
Sorry, I have no ppc hardware too.

@asvetlov
Copy link
Member

Closing, we don't have an access to failed hardware.

@lock
Copy link

lock bot commented Oct 28, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
If you feel like there's important points made in this discussion, please include those exceprts into that new issue.

@lock lock bot added the outdated label Oct 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants