From 079087e299391f6cd1fa5df5e4410faac7f5f2ff Mon Sep 17 00:00:00 2001
From: Arun Babu Neelicattu <arun.neelicattu@gmail.com>
Date: Thu, 16 Apr 2020 04:17:51 +0200
Subject: [PATCH] ci: use tox for cirrus builds

Moving to tox to use isolated buids to avoid some environment specific
dragons in relation to `poetry install` command. Today, the symlinks
will cause issues when poetry attempts to add an editable install into
the venv due to a pathlib2 bug.
---
 .cirrus.yml | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/.cirrus.yml b/.cirrus.yml
index e37c93a5ac2..98088aa6e02 100644
--- a/.cirrus.yml
+++ b/.cirrus.yml
@@ -16,11 +16,9 @@ test_task:
     - pkg install -y git-lite $PYPACKAGE $SQLPACKAGE
   pip_script:
     - $PYTHON -m ensurepip
-    - $PYTHON -m pip install pip -U
-    - $PYTHON -m pip install poetry -U
-    - $PYTHON -m poetry config virtualenvs.in-project true
-  deps_script: $PYTHON -m poetry install
-  test_script: $PYTHON -m poetry run pytest -q --junitxml=junit.xml tests
+    - $PYTHON -m pip install -U pip tox poetry
+    - poetry config virtualenvs.in-project true
+  tox_script: $PYTHON -m tox -e py -- -q --junitxml=junit.xml tests
   on_failure:
     annotate_failure_artifacts:
       path: junit.xml