Re: Flaky dashboard for current branch-2

Thanks for the explanation Appy! bq. I think we can actually update the script to send a mail to dev@ when it encounters these 100% failing tests. Waana try? :) That would be cool, shame people into fixing tests :) I can try to take a look into that. On Fri, Jan 12, 2018 at 5:01 PM, Ted Yu

Re: Flaky dashboard for current branch-2

There is more than one reason. Sometimes QA reported tests in a module failed. When artifact/patchprocess/patch-unit-hbase-server.txt is checked, there were more than one occurrence of the following : https://pastebin.com/WBewfj3Q It is hard to decipher what was behind the crash. Finding

Re: Flaky dashboard for current branch-2

bq. Why a 100% failure test can not be detected with pre commit check? Precommit runs only those tests which are in the modules being changed. If a change breaks downstream modules, it can lead to such a scenario. -- Appy On Fri, Jan 12, 2018 at 4:35 PM, 张铎(Duo Zhang)

Re: Flaky dashboard for current branch-2

Why a 100% failure test can not be detected with pre commit check? Ted Yu 于2018年1月13日 周六07:44写道： > As we get closer and closer to beta release, it is important to have as few > flaky tests as possible. > > bq. we can actually update the script to send a mail to dev@ > > A

Re: Flaky dashboard for current branch-2

As we get closer and closer to beta release, it is important to have as few flaky tests as possible. bq. we can actually update the script to send a mail to dev@ A post to the JIRA which caused the 100% failing test would be better. The committer would notice the post and take corresponding

Re: Flaky dashboard for current branch-2

> Is Nightly now using a list of flakes? Dashboard job was flaky yesterday, so didn't start using it. Looks like it's working fine now. Let me exclude flakies from nightly job. > Just took a look at the dashboard. Does this capture only failed runs or all runs? Sorry the question isn't clear.

Re: Flaky dashboard for current branch-2

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

Re: Flaky dashboard for current branch-2

Dashboard doesn't capture timed out tests, right Appy? Thanks, S On Thu, Jan 11, 2018 at 6:10 PM, Apekshit Sharma wrote: > https://builds.apache.org/job/HBase-Find-Flaky-Tests- > branch2.0/lastSuccessfulBuild/artifact/dashboard.html > > @stack: when you branch out branch-2.0,

Re: Flaky dashboard for current branch-2

Nice job! Thanks Appy! On Fri, Jan 12, 2018 at 6:09 AM, Stack wrote: > Thanks Appy. Looks beautiful. Is Nightly now using a list of flakes? > Thanks. > S > > On Thu, Jan 11, 2018 at 6:10 PM, Apekshit Sharma > wrote: > > >

Re: Flaky dashboard for current branch-2

Thanks Appy. Looks beautiful. Is Nightly now using a list of flakes? Thanks. S On Thu, Jan 11, 2018 at 6:10 PM, Apekshit Sharma wrote: > https://builds.apache.org/job/HBase-Find-Flaky-Tests- > branch2.0/lastSuccessfulBuild/artifact/dashboard.html > > @stack: when you branch

Flaky dashboard for current branch-2

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".