-
Notifications
You must be signed in to change notification settings - Fork 437
chore: use riot for django tests #1760
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if there is a way to validate that the Riotfile was updated to run the same scenarios as tox
?
like tox -l | grep django
compared against riot list
?
.circleci/config.yml
Outdated
command: docker-compose logs -f | ||
background: true | ||
- run: | ||
command: "./scripts/ddtest riot -v run -s 'djangorestframework'" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use something like run_test
for docker builds to abstract this part away?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if there is a way to validate that the Riotfile was updated to run the same scenarios as
tox
?
Updated PR with listing of 69 cases across riot and tox.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we use something like
run_test
for docker builds to abstract this part away?
Yes, definitely think that makes sense but decided to leave that for the next integration we migrate, but can update it here if necessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hehe, or do a starting PR to abstract the docker specific stuff.... then this PR for django :p
I count 68 |
5dcbd92
to
d449065
Compare
d449065
to
13d3b9c
Compare
548a36e
to
4b8bd9f
Compare
4b8bd9f
to
f6ece0c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not the most elegant setup in the circleci config but imo it's readable which is what matters
Description
Replaces tox with riot for django tests.
Also re-enables migration tests which were mistakenly missed with changes in #1744 with filter on
^django_contrib-
rather than^django_contrib
which would capturedjango_contrib_migration
.Total duration of the django CI job goes down from 26 minutes to 11 minutes (before parallelism) and 10 mins to 5 mins (after parallelism).
List of tox envs (=69):
List of riot cases (=69):
Checklist