The 3.1 release of Jinja breaks some part of the Sphinx/nbsphinx
pipeline, causing tutorial jobs to fail. The jinja2 developers consider
this a Sphinx bug, so we need to pin Jinja until a new version of Sphinx
or the nbsphinx extension is released to fix the issue.
stevedore 3.4.0 (used by Terra) issues DeprecationWarning when used with
importlib-metadata 4.7+. Until this is fixed upstream, we pin
importlib-metadata to prevent these errors breaking CI.
importlib-metadata is only relevant on Pythons before 3.8.
* Fix test deprecation warnings and call parent's setUpClass
In Qiskit/qiskit-terra#6753 the base test classes were fixed to assert
that setUp and setUpClass in the base test class are always called. This
is necessary to ensure that all the warning assertions always work.
However this change had the unintended side effect of causing Aer's CI
to fail because it wasn't calling super().setUpClass(). This commit
makes this change to fix that failure. However, because now we're
running enforcement that tests can't raise unhandled
DeprecationWarnings a few spots in the tests were emitting deprecation
warnings. The deprecated syntax is either fixed or if it's testing
something in Aer that's deprecated an assertion on that warning is added
to fix the failure.
* Fix macos tests in CI
Use constrains file when installing deps in running macos tests CI step.
* Update constraints file: numpy<1.20.0
* Fix numpy versions on setup.py and pyproject.toml
* Macos needs numpy installed before attempting to install scs. Also cvxpy 1.1.8 version fails to install, so we constraint to lower versions.
* Leave numpy install to setup.py instead of conda. Use cosntraints in linux and win tests. Cosntrain cvxpy<1.1.8
* Limit numpy version in conda installation, as it is installed by scipy. Remove machine_learning tutorials
* Allow numpy 1.20 in macos
* Fix numpy complex deprecation
* Recover scipy cosntraint
This commit fixes an issue in windows CI around the numpy version and
scipy which is tightly coupled to numpy. In #749 a cap was added to
avoid a broken numpy pre-release version that was getting installed
because an old version of pip was used by the default conda py3.5 env.
This was causing CI faiulres because the pre-release was for 1.19.0
which breaks compat with python 3.5. This pin however is now causing an
issue with scipy (since pip lacks a real dependency solver) because
the latest scipy requires numpy 1.19.0 to work downgrading numpy after
we've installed scipy makes scipy unusable. This commit fixes this by
conda installing both scipy and numpy and no longer pinning the numpy
version prior to running tests.
* Update thrust requirement treatment.
* Added conan info to contributing guide
* Handle thrust TBB & OMP dependency
* Fixed llvm-openmp treatment for macos. Making it shared for python addon.
* Removing unneeded cmake coded regarding third party libraries.
* Removing unneeded distribution of third party libraries.
* Fixes to make travis work. Muparserx fPIC and conan installation for standalone build.
* Disable fpic for muparserx on windows
* Add catch2 to conan packages
* Remove catch2 distributed files
* Conan dep up in file to avoid requirements conflict
* Back to openmp 9.0.1
* Update requires. Remove conan from requirements
* Remove FindXXXX.cmake files not used any more
* llvm-openmp to 8.0.1 to avoid deprecation warning. Added conan.cmake instead of downloading. Removed hack to avoid deprecation warning
* No global include dir. Removed conanfile.txt
* Remove openblas dependencies in ci
* Bump shots from 2000 to 4000 for non-deterministic/random tests
* Bump pin to unify lint job versions across elements
In an effort to unify the versions of pylint run across all the elements
this commit bumps the pinned versions of pylint and astroid to be the
latest and what we are syncing all the elements to use. This should make
working between all the elements easier to do.
Related To: Qiskit/qiskit-terra#3629
* Fix issues introduced by new versions
In a typical example of why we hard pin to a single version for
everything related to pylint in CI the change from 2.4.3 to 2.4.4
introduced a new rule (or changed rule behavior) that caused failures.
This commit fixes those so the new version passes.
* Fix lint failures caused by new pylint and pin
This commit fixes all the issues reported via the newest pylint release.
Several of the rules are bogus failures either because pylint is not
able to inspect c extensions or because it doesn't understand context
and are disabled. In other places they pointed out a couple of
optimizations that can be made to the code. After fixing all the
reported errors this also adds a version pin using a constraints file
to ensure that we have a stable base for lint checking. We can
investigate bumping that pin at the future on our terms instead of
new pylint releases breaking CI periodically.
Jake Lishman