-
Notifications
You must be signed in to change notification settings - Fork 45
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
Timeout tests when they hang. #75
Conversation
Looks like the test suite at least completes now, instead of timing out the AppVeyor build... now to figure out which one it is! |
It's |
I'm not seeing any failing tests anymore. But AppVeyor still returns with a nonzero exit code. What could be the root cause? Also, in one of the passing builds, we still see this in the console output:
|
Perhaps we need to use pytest-xdist's option |
Ugh, it's not supported on Windows... |
Yeah I came accross this before, boxed still isn't supported on windows:
https://bitbucket.org/pytest-dev/pytest/issues/193/xdist-support-for-boxed-on-windows
…On Thu, Aug 10, 2017 at 11:41 PM, Korijn van Golen ***@***.*** > wrote:
I've configured pytest-xdist to box all tests in isolated subprocesses,
and I've removed the skip markers. Let's see if that will give us a decent
overview of test failures...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#75 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAHRQufLLcfPSzY6jrJacAbkExLvy_0pks5sW_eggaJpZM4OzBfS>
.
|
Alright, so, what I've learned in this process is that:
This PR won't help getting AppVeyor builds to pass. Someone really needs to dig into the internals of the library and the tests to figure out what is going on. I've updated #73 to reflect the findings here. This PR can be merged as is. |
@harvimt Can this be merged? |
Hopefully this will snuff out the test that times out on AppVeyor.
Continuation of #74