-
Notifications
You must be signed in to change notification settings - Fork 27
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
🐛 Flaky integration tests relying on migration as a service #4175
🐛 Flaky integration tests relying on migration as a service #4175
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4175 +/- ##
========================================
+ Coverage 80.3% 81.4% +1.1%
========================================
Files 934 957 +23
Lines 40956 41439 +483
Branches 906 952 +46
========================================
+ Hits 32911 33768 +857
+ Misses 7853 7468 -385
- Partials 192 203 +11
Flags with carried forward coverage won't be shown. Click here to find out more. |
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.
very cool. this will help a lot! thanks!
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.
thx!
…-waits-for-migration-service
…b.com:GitHK/osparc-simcore-forked into pr-osparc-fixture-waits-for-migration-service
Code Climate has analyzed commit ddf7751 and detected 0 issues on this pull request. View more on Code Climate. |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
What do these changes do?
Makes
migrated_pg_tables_context
to wait for themigration
service to have finished his migration before proceeding.This impacted all tests requiring a Postgres database and also requesting the
migration
service in thepytest_simcore_core_services_selection
.Tests failed because they usually ran in parallel. This is more evident when the load on the CI is bigger causing delays. Errors such as "field already exists" were showing up in the logs.
Related issue/s
How to test
DevOps Checklist