| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
* Drop testing of Python 2.6, 3.2, and 3.3
* Create 1.12.0-notes.rst and add to source/documentation.
* Update pavement.py to use 1.10.x as LOG_START
* Update version numpy in setup.py
|
| |
|
|
|
|
| |
Also remove all mentions of setupegg.py from the documentation.
|
|
|
|
|
|
|
| |
* shell script style fixes inspired by google shell style guide
https://google.github.io/styleguide/shell.xml
* .travis.yml longline breaking tested with
http://yaml-online-parser.appspot.com/
|
|
|
|
|
|
|
|
|
|
| |
Travis ci is migrating to GCI and the 32 bit tests broke in the process.
This cleans up the tools/travis-test script, fixes it for current
travis, and changes the 32 bit test to use python 2.7 in order to turn
up errors involving python long integers.
In preparation for dropping Python 3.2 and 3.3, the USE_DEBUG test is
run in the travis ci trusty beta so that python3 defaults to 3.4.
|
|
|
|
|
| |
This should ensure the suite stays in working condition, not to produce
reliable timing information.
|
| |
|
| |
|
|
|
|
| |
Python 3.5 has been released, so update 3.5 testing version.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This enables the cache feature of Travis container-based ingrastructure.
Pip's download/build cache is preserved between jobs, speeding up the
install phase.
Installation of nose etc is moved to after pip has been upgraded so that
wheels are favoured.
Sadly this has no effect on Cython - it's still built from source every time.
|
|
|
|
|
|
|
|
|
|
|
| |
All jobs currently run on Travis's legacy infrastructure - which supports sudo.
The newer container-based infrastructure is faster, but doesn't allow sudo.
This patch
- sets sudo=false for all jobs, except the chroot job
- uses Travis's apt addon to install all packages
- installs eatmydata for all jobs to reduce disk IO
- removes the tmpfs workaround for chroot builds
|
|
|
|
|
| |
Python 3.6-dev has broken the nose tester. Use an earlier version
until that gets fixed upstream.
|
| |
|
|\
| |
| | |
TST: re-enable TravisCI testing with Bento.
|
| |
| |
| |
| |
| | |
Disabling was done in gh-5708, due to the Waf download site being down for a
while.
|
|/
|
|
|
|
|
|
|
| |
Module tests whether we can run f2py and return correct version.
Skip this test when running in-place (we don't install f2py in that
case).
Use our own virtualenvs in travis-ci to avoid picking up travis' numpy.
|
|
|
|
|
| |
The waf.io site needed looks to be offline at the moment. This
disables the travis bento build test that depends on it.
|
|
|
|
|
|
|
|
|
|
| |
Rackspace wheels (from http://wheels.scikit-image.org) are giving
timeouts, again - e.g.:
https://travis-ci.org/numpy/numpy/jobs/40578751
Use Nathaniel's trick of not compiling Cython, for speed, and to work
round previous Cython build breakage.
|
|
|
|
|
|
|
| |
Add flag to prevent Cython compiling itself. This speeds Cython
installation and doesn't much slow down pyx file building.
From suggestion by Nathaniel.
|
|
|
|
| |
An attempt to address Cython build failures.
|
|\
| |
| |
| | |
BUG: Make numpy import when run with Python flag '-OO
|
| | |
|
| |
| |
| |
| |
| |
| | |
Remove one of the separate compilation and relaxed strides tests, it is
not worth the cpu time to test these on two python versions.
Use one of them to add a non debug python3.4 test.
|
|\ \
| |/
|/| |
MAINT: start 1.10-devel.
|
| | |
|
|/
|
|
|
| |
Add travis build that builds and installs wheel, runs tests from
installed wheel.
|
|
|
|
|
|
|
| |
Instead generate at build time. The generated sources are still part of
the sdist.
tools/cythonize.py is copied from SciPy with small changes to the
configuration.
|
|
|
|
| |
to do that fix a missing $DIST variable usage in the test script
|
|
|
|
|
| |
python-dbg adds couple extra asserts on reference counts, memory
allocation and also enables a few numpy internal asserts.
|
| |
|
|
|
|
|
|
|
|
| |
Implemented by setting up a chroot in the travis VM and moving all the
test logic, including bento build, to a single script.
This is still reasonable fast, about twice as slow as the normal tests.
When Travis updates to a newer OS it can be replaced by standard cross
compiling.
|
| |
|
| |
|
| |
|
|
|
|
| |
sudo apt-get install -qq libatlas-dev libatlas-base-dev
|
|
|
|
|
|
| |
There's no reason *not* to run the full test suite on Travis, so long
as we fit in under the time limit. And no way to find out if we fit
under the time limit except to try ;-).
|
| |
|
|
|
|
| |
The question has come up sometimes about how much memory etc. we have available for Travis builds. Let's just log the relevant resource limits at the top of every build log.
|
| |
|
|
|
|
|
| |
Done because for 1.8 we're not supporting these Python versions anymore,
and this PR break 2.4 compatibility.
|
|
|
|
|
|
| |
Travis does not support 3.1 anymore, but supports 3.3. See:
https://groups.google.com/d/topic/travis-ci/02iRu6kmwY8/discussion
|
|
|
|
| |
Closes gh-2768.
|
| |
|
| |
|