chore(ci): bring test environment back to life#1269
chore(ci): bring test environment back to life#1269max-wittig merged 9 commits intopython-gitlab:masterfrom
Conversation
This ensures python-dotenv with expected behavior for .env processing
Codecov Report
@@ Coverage Diff @@
## master #1269 +/- ##
=======================================
Coverage 78.05% 78.05%
=======================================
Files 11 11
Lines 2866 2866
=======================================
Hits 2237 2237
Misses 629 629
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
|
Very very nice. I wanted to switch to Github actions for so long, but didn't do it. Thanks! |
max-wittig
left a comment
There was a problem hiding this comment.
Looks very good. Just one question regarding black.
In the end I noticed some of the flakiness in functional tests is still there, but if we don't mind hitting retry on those jobs sometimes we can solve it in a follow-up! :) (e.g. #1215) In that case it's ready. Edit: maybe we need to remove Travis as a required check for this to get merged |
|
I've uninstalled the travis app. I think it should work now. |
The checks run really fast now with GHA. Nice! 🥳 |
|
Soooo fast. Woah. And I had to disable branch protection rules for travis as well. |
|
The tests are flacky because they are not isolated and rely on order of execution, which is not always the same. See: |
|
and create new onces everytime @nejch |
This does a few things to hopefully bring back a workable environment so people's PRs can go green :)
docker-composestarted using python-dotenv which processes .env files differently (at least for paths to env files) and this broke everything in functional tests. This PR explicitly tracks a version in the tox environment so it works everywhere regardless of the system.Edit: well I take that back about tests being stable haha