Some Travis runs take very long #50
Comments
This was referenced Aug 7, 2019
Stewori
pushed a commit
that referenced
this issue
Aug 10, 2019
It is not explicitly stated, which Python versions are supported by Numpy 1.8.2, but Numpy 1.8.0 supports only 2.6 -2.7/3.2 - 3.3 and Numpy 1.9.0 supports only 2.6 - 2.7 and 3.2 - 3.4 [1]. So I propose this change to address [issue 50](#50). [1] https://docs.scipy.org/doc/numpy/release.html
|
Fixed now as of recent commit #53. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In recent Travis run https://travis-ci.org/mdp-toolkit/mdp-toolkit/builds/553703911 I observed that the first two specific configurations took about 14-15 minutes to complete while all other runs took only about 2-5 minutes.
The long-taking runs were Python 3.5 + NumPy 1.8.2 + SciKits 0.18. However a later run with Python 3.5 + NumPy 1.12.1 + SciKits 0.18 was okay so it seems to be caused by NumPy 1.8.2.
It looks like the tests were hanging most time at
test_SFANode.It is difficult to see whether the log contains more useful info because it is totally spammed with the deprecation warning mentioned in #49. So we better fix that one first.
Also, given that the issuous configuration is somewhat odd this doesn't have high priority. I'd like to track it though as it might point to an issue in
test_SFANode.The text was updated successfully, but these errors were encountered: