-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
&yarnabrina [MNT] testing only estimators from modules that have changed compared to main
#5019
Conversation
main
.main
doesn't work like this, errors out with |
Update: this works locally, but not on remote - the reason being, inside the VM we apparently cannot see the For this to work, we need to ensure that FYI @tarpas, any ideas? |
This seems to be working! Testing the positive case with #5023, i.e., the case that two estimator modules change. If that tests exactly those modules with the suite tests, we know it most likely works! |
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.
Thank you so much for this PR. I'll be singificantly happier (at ANY level of significance) if the CI time decreases by running only what's necessary, at least for most of the times (except may be releases?).
I added some comments/doubts/suggestions.
Co-authored-by: Anirban Ray <39331844+yarnabrina@users.noreply.github.com>
This might actually be a case for a CRON job? @hazrulakmal suggested this earlier in another context (checking the upstream data repos' health), here's the link he posted: |
Sure, that'd work. It'll also mean more frequent through testing than what I suggested above as once per new release. But I do have a question, not specifically related to CRON. If we intend to run tests for all estimators, how shall we instruct CI to disregard |
The CRON job uses the flag Similar to how we override |
main
main
main
main
Experimental PR that ensures only estimators are tested that have changed compared to
main
.The design relies on a new utility that checks changes to
main
usingsubprocess
callinggit
.How we know it works:
sktime
, since this PR does not change any of the relevant files.Also, this most likely gets us a good way towards #2890, at least when it comes to tests arising from the
TestAll
portion of the test framework.