-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Understanding an IOError #3145
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
Comments
Seems similar to #2370, at least the symptom. Can you try passing |
I'll give it a try. Thanks |
I'll have to run the packaging multiple times as it's non-deterministic, maybe it'll take a while. Sorry for the randomness. :( |
16 builds passed without any error. What are the cons of the -s option if any? |
|
That's fine with me. I think you solved all my issues. Thanks! I'll leave it open for a little while (let's say a week), and come back at you if I see anything relevant. Cheers! |
@nicoddemus maybe you should remove the bug tag? :) |
If you don't mind I will close this for now, and we can re-open if you see anything relevant that demands some action on pytest's side. 👍
Yep thanks 😁 |
Hi,
I'm packaging for debian some pytest extensions. I submitted a bug to pytest-httpbin (see here: kevin1024/pytest-httpbin#47), regarding some issues with their tests.
Yet, I'm also trying to understand what is going south by myself, and for now, I totally fail at it.
Here's an error I got recently while building the package:
The full test log is here:
As you can see, we use pytest version 3.2.1.
Can you help me to understand where the unsafe "seek" comes from? My guess is that there is an error during the test, and that when pytest tries to capture the stderr, it does a seek but fails as stderr has been closed or something else. So my goal would be to get rid of this error and understand then what is actually not going well?
Thanks!
The text was updated successfully, but these errors were encountered: