Just took a look at the dashboard. Does this capture only failed runs or all runs?
I see that the following tests have failed 100% of the time for the last 30 runs [1]. If this captures all runs, this isn't truly flaky, but rather a legitimate failure, right? Maybe this tool is used to see all test failures, but if not, I feel like we could/should remove a test from the flaky tests/excludes if it fails consistently so we can fix the root cause. [1] master.balancer.TestRegionsOnMasterOptions client.TestMultiParallel regionserver.TestRegionServerReadRequestMetrics Thanks, Zach On Fri, Jan 12, 2018 at 8:19 AM, Stack <st...@duboce.net> wrote: > Dashboard doesn't capture timed out tests, right Appy? > Thanks, > S > > On Thu, Jan 11, 2018 at 6:10 PM, Apekshit Sharma <a...@cloudera.com> > wrote: > > > https://builds.apache.org/job/HBase-Find-Flaky-Tests- > > branch2.0/lastSuccessfulBuild/artifact/dashboard.html > > > > @stack: when you branch out branch-2.0, let me know, i'll update the jobs > > to point to that branch so that it's helpful in release. Once release is > > done, i'll move them back to "branch-2". > > > > > > -- Appy > > >
