Thanks for the information Sean. I will then commit the changes and watch the flaky tests build.
Regards Ram On Tue, Sep 18, 2018 at 11:20 AM Sean Busbey <[email protected]> wrote: > Unfortunately there is not currently a way to have tests that are in > the flaky list run in the automated precommit tests[1]. > > I suggest you test the change locally and then commit. When the test > no longer fails in the flaky test runner and ages out of what the > flaky detector looks at[2], it'll start showing up in precommit again. > > [1]: > > https://issues.apache.org/jira/browse/HBASE-19265 > > [2]: > > > https://builds.apache.org/job/HBase-Find-Flaky-Tests/job/master/lastSuccessfulBuild/artifact/dashboard.html > On Mon, Sep 17, 2018 at 11:59 PM ramkrishna vasudevan > <[email protected]> wrote: > > > > Hi > > > > As part of HBASE-21102 the test case that was added was reported as Flaky > > test. I had fixed the code such that the test case is not flaky any more. > > > > But when we submit the patch for precommit - it still avoids that test > case > > since it is marked flaky. > > > > I can see in the console output that > > DOCKER_EXTRAARGS=--env=EXCLUDE_TESTS_URL= > > > https://builds.apache.org/job/HBase-Find-Flaky-Tests/job/master/lastSuccessfulBuild/artifact/excludes/ > > > > The test TestServerCrashProcedureWithReplicas has been marked in the > > excludes file and hence it is getting skipped. Is there a way to make it > > run again? > > > > I tried asking the question in the JIRA but thought this is the best > place > > to ask. I did check the dev-support folder and the hbase-personality.sh > > file but was not sure if there was a way to include that flaky test back > > again to ensure it starts running again. > > > > Regards > > Ram >
