-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
All NotebooksTestCase tests fail with CalledProcessError
#275
Comments
Is I have seen that error when I have only installed |
I've had a similar issue. Notebook tests failed on my local machine. The main line of interest in my case was I am working with Conda and it's environments; the same issue was discussed here. I adapted the solution, and it worked! In my case, the system's python installation
These are links to the system's python installations (without tsfresh and dependencies installed), which were apparently called by
I ran the test
I don't know if it's the same in Use it on your own risk. Please let me now what the issue was. This solves my post / experience I reported in a former issue as well. |
@MaxBenChrist do you run tests locally? Do they pass? What is your setup? virtualenv, system python or conda? Thx for info. |
@nikhaas virtualenv, Mac OS or Ubuntu 16.04, no problems so far. |
Thanks for the hints @nikhaas and @MaxBenChrist. However, the strange thing is, that running the tests at a later time actually worked out. I do not have the time to investigate this, but we should keep in mind, that this can be a source of errors. |
As this error did not show up again and we excluded notebook tests from the test suite I close this now |
Relevant output:
and
I have the same problem with running the tests with Python 3.
The relevant code of the tests seems to be:
Apparently these settings don't work on my machine (Fedora 26).
The text was updated successfully, but these errors were encountered: