You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 14, 2022. It is now read-only.
Does not seem like its urgent, but running a time-limited analysis on something as big as scikit-learn (see #379) before merging pull requests would alleviate some unnoticed regressions.
The text was updated successfully, but these errors were encountered:
Running automated tests on PRs and such, which is already covered by Set up CI with tests on Windows, Mac and Linux #352, but may need to wait until we simplify things to the point where running the suite doesn't take half an hour.
Running tests on big complicated codebases like scikit-learn, which we might not really be able to do either until we remove the slow analyzer either (from experience running it on scikit-learn takes a good 20 minutes even when I do it from /tmp).
@jakebailey I think tests can still be run on scikit-learn, or any other large project as long as they are time- or iteration-limited. E.g. just have AnalyzeQueuedEntries called with a timed cancellation token, or cancel it as soon as, say, 100000 units have been (re-)analyzed. The later option would be more stable.
Does not seem like its urgent, but running a time-limited analysis on something as big as scikit-learn (see #379) before merging pull requests would alleviate some unnoticed regressions.
The text was updated successfully, but these errors were encountered: