| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Revert the temporary workaround changes from NumPy gh-16147 now that
the manylinux2010_i686 has been updated to be compatible with the
pre-built version of OpenBLAS used. See NumPy gh-16146 for details.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Azure CI is currently failing Linux 32-bit job
because of a gcc toolchain bump in the base manylinux2010
image (32-bit) from ~12 hours ago; see NumPy gh-16146 for
details; in short, we can't link to OpenBLAS in that matrix
entry because the libgfortran in the new manylinux2010 image
is too new
* as a temporary workaround to constant CI failure, pin the
base image to a tag from a few days ago, before the gcc toolchain
update was merged
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
* TST: Test during import to detect bugs with Accelerate(MacOS) LAPACK
fixes #15647
* Pipeline update for Accelerate(MacOS) testing
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Azure-pipelines is currently experiencing an "incident":
https://status.dev.azure.com/_event/179641421)
From that web page:
> Currently CI and PR triggers in YAML for GitHub and Bitbucket
> repositories are not working when they are not explicitly listed
> in the YAML file. Our expected behavior is that when there are
> no explicit triggers in the YAML, the pipelines will trigger on
> all commits on all branches and all pull requests. This is
> currently not happening. To workaround, please explicitly list
> the triggers you want in the YAML file for your pipeline.
This PR adds the suggested explicit 'pr' triggers to the YAML file.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The gfortran link is preinstalled since Feb 13, 2020 and attempting to
create the link causes an error to be raised.
|
| |
|
| |
|
|
|
|
| |
Adapt CI scripts to this.
|
| |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
So that not so many resources are used on obviously failing jobs.
|
| |
|
|\
| |
| | |
DOC: support and require sphinx>=2.2
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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)
|
|
|
|
|
|
| |
This is a follow-up to gh-7427. This can lead to hard to understand
build failures, and we've warned that this change was coming for two
releases.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
* bump OpenBLAS version to 0.3.7.dev
in Azure CI to pick up AVX512 SkylakeX
fixes and match wheels
* use ctypes code to verify appropriate
version of OpenBLAS
|
|
|
|
|
|
|
|
|
|
| |
* Azure CI should no longer report
success when there are failures
outside of the test suite
* Azure CI will still always try
to publish test results, except
when a pipeline is manually cancelled
|
| |
|
| |
|
| |
|
|
|
|
|
| |
* fail Azure CI after test publication
when there are test failures
|
|
|
|
|
|
|
| |
* add Azure configuration directives
to ensure that CI test results are
always published, even in the case
where there are test failures
|
| |
|