1. 15 Jan, 2019 2 commits
    • Anusree's avatar
      Remove py26 support · 8266c8de
      Anusree authored
      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
    • Chih-Hsuan Yen's avatar
      Get rid of psycopg2 warnings by disabling wheels · f44d0795
      Chih-Hsuan Yen authored
      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
  2. 05 Jul, 2015 1 commit
    • Matt Riedemann's avatar
      Update flake8 related dependencies · dc07f8de
      Matt Riedemann authored
      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
  3. 29 Jan, 2015 1 commit
    • Mike Bayer's avatar
      Add pretty_tox setup · 997855db
      Mike Bayer authored
      This changeset adds the pretty_tox script runner to SQLAlchemy-migrate,
      so that current test runs can be viewed clearly.
      Change-Id: I3884703e24cb636983a0202c46899c772419d401
  4. 03 Sep, 2014 1 commit
  5. 23 Aug, 2014 1 commit
  6. 09 Apr, 2014 1 commit
    • Cyril Roelandt's avatar
      Port to Python3 · a03b141a
      Cyril Roelandt authored
      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
      Thanks to Victor Stinner who co-wrote this patch.
      Change-Id: Ia6dc536c39d274924c21fd5bb619e8e5721e04c4
      Co-Authored-By: 's avatarVictor Stinner <victor.stinner@enovance.com>
  7. 05 Mar, 2014 1 commit
    • Sean Dague's avatar
      turn on testing for sqla 0.9 · 0b08e91d
      Sean Dague authored
      this enables tox testing for the sqla 0.9 changes, and provides
      new targets for sqla 0.9 and 0.8.
      Change-Id: I297dce0267bd10cd7db0fe270945c8e5a3431167
  8. 23 Feb, 2014 1 commit
    • Sean Dague's avatar
      uncap SQLA in requirements.txt · fe148d87
      Sean Dague authored
      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
  9. 12 Oct, 2013 1 commit
    • Roman Podolyaka's avatar
      Run tests on PostgreSQL and MySQL too · a91766a1
      Roman Podolyaka authored
      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
  10. 07 Oct, 2013 1 commit
    • Monty Taylor's avatar
      Update tox requirements · 838c1cbb
      Monty Taylor authored
      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
  11. 05 Aug, 2013 1 commit
    • Roman Podolyaka's avatar
      Run tests with different SQLAlchemy versions · ddea3a8b
      Roman Podolyaka authored
      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
  12. 11 Jul, 2013 2 commits