-
Notifications
You must be signed in to change notification settings - Fork 17
MNT: Execute slowest tests on schedule #258
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
base: master
Are you sure you want to change the base?
Conversation
@effigies I am not happy with this duplication, but did not find a better way to try to do this: |
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.
43b21f7
to
8a2071a
Compare
Please, feel free to take over; I thought that issue #229 referred to Python testing purely, so did not have a look at what are other bottlenecks. I am not sure the current approach is working well either, since I do not see the GitHub checks taking place on the commit event. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #258 +/- ##
=======================================
Coverage 96.74% 96.74%
=======================================
Files 16 16
Lines 1994 1994
Branches 267 267
=======================================
Hits 1929 1929
Misses 41 41
Partials 24 24
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
590f746
to
197405b
Compare
Execute slowest tests on schedule. Co-authored-by: Chris Markiewicz <effigies@gmail.com>
Drop 3.9 from tested Python version matrix. Co-authored-by: Oscar Esteban <code@oscaresteban.es>
197405b
to
34e33e7
Compare
Execute slowest tests on schedule.
Fixes #229.