[
https://issues.apache.org/jira/browse/KUDU-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Greber updated KUDU-3435:
--------------------------------
Summary: Test newly added tests for flakiness (was: Test newly added tests
for flakyness)
> Test newly added tests for flakiness
> ------------------------------------
>
> Key: KUDU-3435
> URL: https://issues.apache.org/jira/browse/KUDU-3435
> Project: Kudu
> Issue Type: Improvement
> Reporter: Marton Greber
> Priority: Minor
> Labels: build, flaky-test
>
> Lately the number of flaky tests grew. In order to combat this, it was
> discussed to encourage contributors to run newly added tests multiple number
> of times before submission. Obviously tests can become flaky over time etc,
> but this would be a step in the right direction to tackle the increasing
> number of flaky tests.
> To better integrate this into the developer workflow, it would be nice to add
> this kind of testing to the existing test suite. The main script for building
> and testing can be found here:
> [https://github.com/apache/kudu/blob/master/build-support/jenkins/build-and-test.sh]
> It would be necessary to modify this script, to check if a new test is being
> added (git show with some filtering), and then run the new test using
> appropriate setting for --gtest_filter say, for 100 times by running
> ../../build-support/dist_test.py loop -n 256 -- $test_fpath
> --stress_cpu_threads=16.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
