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

travis tests #74

Closed
tolgayapici opened this issue Aug 2, 2017 · 3 comments
Closed

travis tests #74

tolgayapici opened this issue Aug 2, 2017 · 3 comments

Comments

@tolgayapici
Copy link

as i was looking at the failure messages on travis tests, I realize that none of the tests for testing different versions of numpy actually uses the version in the config file.
for a similar reason, in the dithering branch and in my pull request, one of the tests is failing because numpy version 1.13 only works for Python version 2.7 or >= 3.4.

@dkirkby
Copy link
Member

dkirkby commented Jul 26, 2018

@tolgayapici Can you give a bit more detail on the issue here? If I look at this recent travis log which is configured to use numpy 1.10, I see, for example:

$ export NUMPY_VERSION=1.10
...
The following NEW packages will be INSTALLED:

    mkl:   11.3.3-0     
    numpy: 1.10.4-py35_2
...
Numpy: 1.10.4
...

It looks like the test is using the specified version.

@weaverba137
Copy link
Member

Aside from determining which numpy version is being tested, hopefully at least some tests are using 1.13 & 1.14. 1.10 is getting old at this point.

@dkirkby
Copy link
Member

dkirkby commented Jul 26, 2018

We are currently testing numpy 1.10, 1.11, 1.12 and "prerelease". I agree this should be updated but that's a separate issue, so I am closing this now.

@dkirkby dkirkby closed this as completed Jul 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants