Hi all,

Production deployments of Patchwork often use postgres instead of
mysql. So far we haven't been testing that very well, and so when
OzLabs was upgraded some bugs were discovered. jk has kindly sent
patches to fix the fuzztest failures.

We also saw errors due to ordering - one of Stephen's Django 1.11
patches fixes that, so pull it in here.

Patches 2-4 support better testing for postgres. Patch 3 allows local
testing, and patch 4 does automatic testing in Travis with a nice
recent version.

I haven't tried the rest of the Django 1.11 series on postgres, but
that's next on my list.

v1-v2: Fixup various review comments.
       Replace my patch 1 with Stephen's Django 1.11 patch

Regards,
Daniel

Daniel Axtens (3):
  Simplify docker-compose MySQL setup
  Support testing with PostgreSQL
  Test postgresql support in Travis CI

Stephen Finucane (1):
  REST: Specify default ordering fields

 .travis.yml                   | 10 ++++++++-
 docker-compose-pg.yml         | 30 +++++++++++++++++++++++++++
 docker-compose.yml            |  9 +++++++--
 patchwork/api/bundle.py       |  1 +
 patchwork/api/check.py        |  1 +
 patchwork/api/cover.py        |  1 +
 patchwork/api/event.py        |  5 ++---
 patchwork/api/patch.py        |  1 +
 patchwork/api/person.py       |  1 +
 patchwork/api/project.py      |  1 +
 patchwork/api/series.py       |  1 +
 patchwork/api/user.py         |  1 +
 requirements-test.txt         |  3 ++-
 tools/docker/Dockerfile       |  2 +-
 tools/docker/db/.dockerignore |  1 -
 tools/docker/db/Dockerfile    | 10 ---------
 tools/docker/entrypoint.sh    | 47 ++++++++++++++++++++++++++++++++++---------
 17 files changed, 97 insertions(+), 28 deletions(-)
 create mode 100644 docker-compose-pg.yml
 delete mode 100644 tools/docker/db/.dockerignore
 delete mode 100644 tools/docker/db/Dockerfile

-- 
2.11.0

_______________________________________________
Patchwork mailing list
Patchwork@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/patchwork

Reply via email to