-
Notifications
You must be signed in to change notification settings - Fork 18
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
Fix notebook tests #630
Fix notebook tests #630
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #630 +/- ##
=======================================
Coverage 83.61% 83.61%
=======================================
Files 16 16
Lines 3522 3522
=======================================
Hits 2945 2945
Misses 577 577
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
pytest-docker~=3.1.0 | ||
pytest-selenium~=4.1.0 | ||
pytest-timeout~=2.3.0 |
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.
To be on the safe side and to reduce potential churn, let's pin all test dependencies to minor versions.
@edan-bainglass please take a look. Ideally we merge this first so other PRs can have tests passing. |
Going to land this now as I will be AFK for the next two hours. |
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.
Hopefully increasing the time is sufficient. LGTM!
The last successfully run of notebook tests is from July 8. There were no code changes that should impact the tests, we need to investigate what changed since then.
EDIT: It looks like just increasing the wait time tolerance fixes the issue. Perhaps the github runners just got slower? Not sure.