| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Co-authored-by: Matti Picus <matti.picus@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This guard protects against any sudden unexpected changes that may adversely
affect the compile-time SIMD features detection which could leave the SIMD code
inactivated. Until now we have faced two cases:
1. Hardening the compile-time test files of Neon/ASIMD features without checking
the sanity of the modification leading to disabling all optimizations on aarch64.
see gh-21747
2. A sudden compiler upgrades by CI side on s390x that causes conflicts with the
installed assembler leading to disabling the whole VX/E features, which made us
merge SIMD code without testing it. Later, it was discovered that this code
disrupted the NumPy build.
see gh-21750, gh-21748
|
| |
|
| |
|
|
|
|
|
| |
This allows to share the configuration between GitHub Actions and Travis-CI.
This also allows to easily run cibuildwheel locally to debug build issues when they arise.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This is in preparation for dropping Python 3.7. It also allows the
use of name-only arguments in function signatures.
|
|
|
|
|
| |
This reverts to using arm64 instead of arm64-graviton2 now that
OpenBLAS has been updated to 0.3.16.
|
| |
|
|
|
|
|
| |
This avoids the errors we have seen with the lxd containers
in recent weeks.
|
|
|
|
|
| |
The arm64 builds are failing to run, both for NumPy wheels and for
NumPy main using bionic. Try focal instead.
|
|
|
|
|
|
|
|
| |
The default clone depth of TravisCI is 50, which is insufficient to make
the most recent annotated tag visible to versioneer now that master is
has grown to 579 commits past the tag. Disabling the clone depth as
suggested at https://docs.travis-ci.com/user/customizing-the-build/
appears to solve the problem.
|
| |
|
| |
|
|
|
|
|
| |
Travis didn't recognize aarch65 and ran amd_64 instead. This
also fixes a compiler warning that turned up on with the fix.
|
|
|
|
|
|
|
| |
The DEBUG test requires the debug version of Python which is only
available for the default Python of the Ubuntu version being used. The
latest available LTS version available for TravisCI looks to be Focal
Fossa (20.04 LTS) which supports Python 3.8. Give it a shot.
|
| |
|
|
|
|
| |
Disable testing with Python 3.9-dev until a fix for the current
failures is forthcoming. The test failures are annoying.
|
| |
|
| |
|
|
|
|
|
|
|
| |
PR #6768 introduced the uploading of wheels built during travisCI
testing to a Rackspace account. We are moving away from Rackspace and
already produce more complete sets of wheels for development testing on
a weekly schedule. Consequently those wheels are not longer useful.
|
|
|
|
|
|
|
| |
Remove support for Apple Accelerate, since it is buggy. A build error should
occur on most or all setups if linked against Accelerate. Test or import failures
should occur on setups where Accelerate is picked up dynamically.
Co-authored-by: Warren Weckesser <warren.weckesser@gmail.com>
|
|
|
|
| |
Co-authored-by: Charles Harris <charlesr.harris@gmail.com>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The comments in .travis.yml say
# After changing this file, check it on:
# http://lint.travis-ci.org/
When I do that, I get the following from the linter:
```
[warn] on root: unknown key "stage" (Comprehensive tests)
[info] on root: the key matrix is an alias for jobs, using jobs
[info] on root: missing os, using the default "linux"
```
This commit fixes the issues reported in those messages.
|
|
|
|
|
|
|
| |
Apart from the usual modifications, this
- Removes a release note snippet added after towncrier was run
- Removes testing on Python 3.5 as it is dropped for 1.19.x.
|
|
|
|
|
| |
- Use 3.8 instead of 3.8-dev
- Add some blank lines for clarity
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* for those cases where our CI uses an OpenBLAS backend
for testing it has now been updated to use v0.3.7 stable release
instead of a commit hash on the development branch preceding that
release
* the pre-built OpenBLAS binaries are pulled in from either the
MacPython ecosystem (most architectures) or from a custom build
script for ARMv8 and ppc64le architectures used on gcc compile farm machines
(documented in openblas_support module)
|
|
|
|
|
|
|
| |
Pytest-5.1.0 segfaults on python3.5-dbg. Because we will be
dropping 3.5 for NumPy 1.18 we might as well use Python3.6
for the debug testing. That cures the previous segfault,
but exposes another so we also pin pytest to 5.0.1.
|
| |
|
|
|
|
|
| |
* require OpenBLAS 0.3.7.dev in ARMv8
and POWER8 CI runs to match ecosystem / wheels
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* add a function to tools/openblas_support.py
that may be used to test OpenBLAS version
available through NumPy in a manner agnostic
to any specific CI service
* expand OpenBLAS version checking to include
ppc64le and POWER8 CI runs; a separate PR will
be provided to bump these versions to 0.3.7.dev
* OpenBLAS install was broken on ppc64le
Travis CI after migration to tools/openblas_support.py;
fixed that
* Azure CI config no longer uses a single-line
280-character Python "program" assigned to an
environment variable to check OpenBLAS version;
instead, it now leverages tools/openblas_support.py
to perform the same operation using a conventional
Python function
|
|
|
|
|
|
|
| |
Ubuntu 14.04 LTS (Trusty) provided a long term support distribution of
Ubuntu with a 5 year support window. This window ended in April 2019
and Trusty is now no longer supported. This commit removes Trusty from
the Travis-CI build.
|
| |
|
|\
| |
| | |
BLD: Allow users to specify BLAS and LAPACK library link order
|
| |
| |
| |
| | |
Signed-off-by: Nick Papior <nickpapior@gmail.com>
|
| |
| |
| |
| |
| |
| |
| | |
Also added a test to travis (apparently ATLAS=None... is not tested
on circleCI).
Signed-off-by: Nick Papior <nickpapior@gmail.com>
|
|/ |
|