This adds the voting and gating openstack-tox-py36 job
and adds python 3.6 to the classifiers list.
Change-Id: Ida2349de534399103e5d6f294a7e771910188ee4
This makes the openstack-tox-py35 job voting and gating
and adds python 3.5 to the classifiers list.
Change-Id: I11c8cd0e33e0609d740f5742096438a2395b28ed
We can control python version sensitive dependencies
in the single test-requirements.txt file so we can
drop the version-specific files. This should also make
the openstack-tox-py35 job start passing.
Change-Id: Ic3fa2c4417092e387ac5d177be75a22050a6f857
This adds a minimal bindep.txt to install mysql and postgresql
dependencies (copied from nova's bindep.txt). This is needed
now to get python jobs (pep8,py27,etc) working in the gate.
Change-Id: I4b7bccdb7cebd95753e8cd931846213f400aa652
Closes-Bug: #1836087
Support for python 2.6 was dropped in commit
8266c8dec0 but the
tox targets were missed, so they are removed here.
Change-Id: I2271717ce4a35183d2b773063564cbaf774fdfb0
Fixes for docs build:
* Use doc/requirements to follow changes in OpenStack CI for the docs
building, add a tox environment for this.
* Remove reference to "project's download page", the link was removed in
change I2db594d279e1229e5b1600cecad86fe0c3612115 and now we have a
dead link that errors building if warnings are treated as errors.
* Change I2db594d279e1229e5b1600cecad86fe0c3612115 added a column for
DB2 header but not for any entries, enhance table with extra column.
This fixes building of the table if warnings are treated as errors.
* Update to sphinx 1.6.x since that is what is used in OpenStack CI job,
remove issuetracker, it does not work with sphinx 1.6 anymore.
* Disable html_static_path - the content does not exist
* Use python3 for docs building
Change-Id: I76ee4d6dc45f9b04115f093951ae8b745f3ac026
As of mitaka, the infra team won't have the resources available to
reasonably test py26, also the oslo team is dropping py26 support
from their libraries. sine we rely on oslo for a lot of our work,
and depend on infra for our CI, we should drop py26 support too.
Change-Id: I6af3716f5daf73febdabcd79853a09512428c289
Closes-Bug: 1519510
The psycopg2 wheel package warnings are causing some tests
to fail which expect there to be no stderr output. This fixes
the problem by not using the wheel binary for that package.
Closes-Bug: #1811876
Change-Id: Id43e74d8d343ab4e80d1d246543bada1ed4d06ad
In order to raise the cap on pbr we need to update
the dependent versions of the flake8 related packages
for the pep8 job since they have capped pbr.
A couple of simple hacking issues are fixed, the rest
are ignored.
Change-Id: Icddb5bf284da7b6463ebcfc7512726149ffe6085
This changeset adds the pretty_tox script runner to SQLAlchemy-migrate,
so that current test runs can be viewed clearly.
Change-Id: I3884703e24cb636983a0202c46899c772419d401
Brief summary of the modifications:
* Use six for compatibility with both Python 2 and 3;
* Replace UserDict.DictMixin with collections.MutableMapping;
* Fix relative imports;
* Use test-requirements.txt for requirements that are common to both Python 2
and 3, and test-requirements-py{2,3}.txt for version-specific requirements;
* Miscellaneous fixes.
* Use a specific test_db_py3.cfg file for Python 3, that only runs tests on
sqlite.
Thanks to Victor Stinner who co-wrote this patch.
Change-Id: Ia6dc536c39d274924c21fd5bb619e8e5721e04c4
Co-Authored-By: Victor Stinner <victor.stinner@enovance.com>
migrate can't just take a global requirements sync because it
needs to be tested against multiple versions of SQLA to assure
compatibility. A recent change had the effect of only testing
migrate against SQLA 0.7, which is definitely *not* what we
want to be doing.
this reverts that change, and leaves very specific comments to
hopefully prevent this from happening in the future.
Change-Id: Icb4e136f0de6caa224019bb955341c4b67c5e1a1
In addition to running tests with different Python and SQLAlchemy
versions, they should also be run on different DB backends, which
are used in production (PostgreSQL and MySQL).
This patch:
- modifies test_db.cfg to run tests on PostgreSQL and MySQL
(Jenkins Slave credentials are used here, to ensure these
tests are always run by Jenkins gate); if a backend is not
available, test cases will be skipped for it
- concurrency is set to 1 (sharing of the one MySQL or PostgreSQL
DB among different test runner processes would lead to
race conditions)
- fixes tests dropping FK columns in MySQL: in earlier MySQL
versions dropping a column that is a part of a FK constraint
would lead to dropping of the FK too. As of MySQL 5.5 that's
not the case anymore: if one tries to drop such column, he/she
will get a very obscure error (something like "Error on rename
of './openstack_citest/#sql-4af_aa2' to './openstack_citest/tmp_adddropcol'
(errno: 150)") '\nALTER TABLE tmp_adddropcol DROP COLUMN r2').
So the solution if to drop FK constraints first, and only then
the columns it is made up of
Change-Id: I8c5d2874c83e7df46da69969ed54d85437c849e7
Update to needing 1.6, which gives us the ability to alter how the
software is installed into the virtualenv. It also brings in pip 1.4,
which lets us avoid getting pre-releases of things we weren't expecting.
Change-Id: I3189f06610d776a032b5f8bf0910f59e4ed45719
The test suite should be run for all possible combinations
of Python and SQLAlchemy versions we claim to support, which
are Python 2.6 and 2.7 and SQLAlchemy 0.7.x (old stable) and
0.8.x (mainline stable).
py26/py27 tox envs install the latest stable version of SQLAlchemy
(currently, 0.8.x branch), so two additional tox environments added
to run the test suite with SQLAlchemy 0.7.x (for both Python 2.6 and 2.7).
Change-Id: I50c7009d8b808ce3bbb1f0a27c50f5cb5116cdb3
Matt Riedemann