You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/01/17 18:18:00 UTC
[jira] [Updated] (GEODE-6147) Fail benchmark junit tests if their
numbers deviate too far from a baseline
[ https://issues.apache.org/jira/browse/GEODE-6147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated GEODE-6147:
----------------------------------
Labels: pull-request-available (was: )
> Fail benchmark junit tests if their numbers deviate too far from a baseline
> ---------------------------------------------------------------------------
>
> Key: GEODE-6147
> URL: https://issues.apache.org/jira/browse/GEODE-6147
> Project: Geode
> Issue Type: Improvement
> Components: benchmarks
> Reporter: Dan Smith
> Assignee: Sean Goller
> Priority: Major
> Labels: pull-request-available
>
> We want to fail tests if performance gets worse. We also want a signal to create a new baseline if performance gets better, so perhaps we should fail tests in that case as well.
> One way to do this would be to add a new system property to the TestRunners.defaultRunner() that takes in a baseline directory. The test itself could compare it's results with the baseline after running and fail if it deviates too far from the baseline.
> Using that, we could a new flag to the benchmark task to pass in that baseline and cause tests that deviate to fail.
> Eg
> ./gradlew benchmark -Pbaseline=/some/dir
> Acceptance:
> run_against_baseline.sh generates a failure report if benchmarks deviate too far from the baseline.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)