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 has been archived by the owner on May 17, 2022. It is now read-only.
Ideally using scikit-validate, the pipeline would benchmark it's performance, and also compare that no distributions have changed (unless this is expected). Since this is a nightly build and not a Merge Request, there'd need to be some consideration for how to report these results back, nightly email? Issue opened if things change in unexpected ways?
The text was updated successfully, but these errors were encountered:
That is doable. For LZ + scikit-validate we have the bot posting to an MR but the same can be done for an issue.
What you need to define, and that's WIP for skvalidate, is what warrants a big enough problem for a test to fail.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Imported from gitlab issue 4
Ideally using scikit-validate, the pipeline would benchmark it's performance, and also compare that no distributions have changed (unless this is expected). Since this is a nightly build and not a Merge Request, there'd need to be some consideration for how to report these results back, nightly email? Issue opened if things change in unexpected ways?
The text was updated successfully, but these errors were encountered: