blob: 38b1ec0c971de8098e3f13668fb6a8b6dc8ca74e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
|
# After changing this file, check it on:
# http://lint.travis-ci.org/
language: python
python:
- 2.6
- 2.7
- 3.2
- 3.3
matrix:
include:
- python: 2.7
env: NPY_SEPARATE_COMPILATION=0
- python: 3.3
env: NPY_SEPARATE_COMPILATION=0
- python: 2.7
env: NPY_RELAXED_STRIDES_CHECKING=1
- python: 3.3
env: NPY_RELAXED_STRIDES_CHECKING=1
before_install:
- uname -a
- free -m
- df -h
- ulimit -a
- mkdir builds
- pushd builds
- pip install nose
# pip install coverage
- python -V
- sudo apt-get install -qq libatlas-dev libatlas-base-dev
- popd
install:
# We used to use 'setup.py install' here, but that has the terrible
# behaviour that if a copy of the package is already installed in
# the install location, then the new copy just gets dropped on top
# of it. Travis typically has a stable numpy release pre-installed,
# and if we don't remove it, then we can accidentally end up
# e.g. running old test modules that were in the stable release but
# have been removed from master. (See gh-2765, gh-2768.) Using 'pip
# install' also has the advantage that it tests that numpy is 'pip
# install' compatible, see e.g. gh-2766...
- pip install .
script:
# We change directories to make sure that python won't find the copy
# of numpy in the source directory.
- mkdir empty
- cd empty
- INSTALLDIR=$(python -c "import os; import numpy; print(os.path.dirname(numpy.__file__))")
- export PYTHONWARNINGS=default
- python ../tools/test-installed-numpy.py --mode=full
# - coverage run --source=$INSTALLDIR --rcfile=../.coveragerc $(which python) ../tools/test-installed-numpy.py
# - coverage report --rcfile=../.coveragerc --show-missing
notifications:
# Perhaps we should have status emails sent to the mailing list, but
# let's wait to see what people think before turning that on.
email: false
|
