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

pexpect using tests regulary hang/die #2673

Closed
RonnyPfannschmidt opened this issue Aug 9, 2017 · 14 comments
Closed

pexpect using tests regulary hang/die #2673

RonnyPfannschmidt opened this issue Aug 9, 2017 · 14 comments
Labels
status: critical grave problem or usability issue that affects lots of users status: needs information reporter needs to provide more information; can be closed after 2 or more weeks of inactivity type: bug problem that needs to be addressed type: infrastructure improvement to development/releases/CI structure

Comments

@RonnyPfannschmidt
Copy link
Member

we pretty much have broken tests there,
whenever i have pexpect installed, py.test hangs testing terminal or pdb

@RonnyPfannschmidt RonnyPfannschmidt added type: bug problem that needs to be addressed status: critical grave problem or usability issue that affects lots of users type: infrastructure improvement to development/releases/CI structure status: needs information reporter needs to provide more information; can be closed after 2 or more weeks of inactivity labels Aug 9, 2017
@RonnyPfannschmidt
Copy link
Member Author

i keep hitting this one, i'm tempted to just remove pexpect since its all broken atm

@nicoddemus
Copy link
Member

That doesn't happen on CI though does it?

@RonnyPfannschmidt
Copy link
Member Author

yes, which makes it even more of a pain, since ithappens in tox/local usage and its typically due to badly set timeouts/interactions in each test

@nicoddemus
Copy link
Member

In this case I would think twice about removing it, specially if we can't pin point the actual cause and it currently passes on CI.

@RonnyPfannschmidt
Copy link
Member Author

what value does a test have, where we dont know why it works when it works

@nicoddemus
Copy link
Member

I thought the pexpect tests ensured that user interaction work as expected in situations like --pdb. I never took a deeper look at them though.

@RonnyPfannschmidt
Copy link
Member Author

@nicoddemus all i know that they regularly fall apart for me - and its starting to be really irritating

@srinivasreddy
Copy link
Contributor

I can confirm this on my local.
image

@stanislavlevin
Copy link

ping

@RonnyPfannschmidt
Copy link
Member Author

it wont pong, its hanging

@blueyed
Copy link
Contributor

blueyed commented Apr 7, 2019

Is this still happening for you?

I've noticed "hacks" / code for Mac OS, but are you all using MacOS for when it happens/hangs?
(never seen it myself on Linux)

@blueyed
Copy link
Contributor

blueyed commented Apr 7, 2019

So if you're seeing this, please use -vv to see the test that hangs.. see #3116 for a possible fix in this regard.

@nicoddemus
Copy link
Member

Closing as no more information has been provided. We can reopen once the suggestion by @blueyed has been tried. 👍

@blueyed
Copy link
Contributor

blueyed commented May 27, 2019

Turns out you have to read() with pending output before wait() - likely related to different behavior with regard to output buffering then maybe, but #5313 should fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: critical grave problem or usability issue that affects lots of users status: needs information reporter needs to provide more information; can be closed after 2 or more weeks of inactivity type: bug problem that needs to be addressed type: infrastructure improvement to development/releases/CI structure
Projects
None yet
Development

No branches or pull requests

5 participants