Skip to content
This repository has been archived by the owner on May 17, 2022. It is now read-only.

Add benchmarking and physics validation of outputs to pipeline #4

Open
benkrikler opened this issue Oct 6, 2019 · 1 comment
Open
Assignees
Labels
originally gitlab For items that were originally created on gitlab and imported over pipeline

Comments

@benkrikler
Copy link
Member

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?

@benkrikler benkrikler added originally gitlab For items that were originally created on gitlab and imported over pipeline labels Oct 6, 2019
@benkrikler benkrikler self-assigned this Oct 6, 2019
@kreczko
Copy link

kreczko commented Oct 7, 2019

Issue opened if things change in unexpected ways?

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
originally gitlab For items that were originally created on gitlab and imported over pipeline
Projects
None yet
Development

No branches or pull requests

2 participants