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,

[jira] [Created] (HBASE-19784) stop-hbase gives unfriendly message when local hbase isn't running

Mike Drob created HBASE-19784: - Summary: stop-hbase gives unfriendly message when local hbase isn't running Key: HBASE-19784 URL: https://issues.apache.org/jira/browse/HBASE-19784 Project: HBase

[jira] [Reopened] (HBASE-19694) The initialization order for a fresh cluster is incorrect

[ https://issues.apache.org/jira/browse/HBASE-19694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack reopened HBASE-19694: --- > The initialization order for a fresh cluster is incorrect >

Re: [VOTE] The third hbase-2.0.0-beta-1 Release Candidate is available for download

There seem to be too many tests failing for this to pass. Just a heads up that if you are seeing this, its not you. I'm looking at it. Will report back. FYI, I need to look into RC-building time too. It takes many hours to produce one. Thanks, S On Thu, Jan 11, 2018 at 10:30 PM, Stack

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: [VOTE] The third hbase-2.0.0-beta-1 Release Candidate is available for download

The bulk of the build time seems due to the retargeting of the Maven repository cache to a new empty directory, requiring a jarcrawl of the world at every build. If we had a flag to make this optional and nondefault I bet that would resolve it. > On Jan 12, 2018, at 9:31 AM, Stack

Re: [VOTE] The third hbase-2.0.0-beta-1 Release Candidate is available for download

On Fri, Jan 12, 2018 at 9:37 AM, Andrew Purtell wrote: > The bulk of the build time seems due to the retargeting of the Maven > repository cache to a new empty directory, requiring a jarcrawl of the > world at every build. If we had a flag to make this optional and

[jira] [Created] (HBASE-19787) Fix or disable tests broken in branch-2 so can cut beta-1

stack created HBASE-19787: - Summary: Fix or disable tests broken in branch-2 so can cut beta-1 Key: HBASE-19787 URL: https://issues.apache.org/jira/browse/HBASE-19787 Project: HBase Issue Type:

[jira] [Resolved] (HBASE-19787) Fix or disable tests broken in branch-2 so can cut beta-1

[ https://issues.apache.org/jira/browse/HBASE-19787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-19787. --- Resolution: Fixed Pushed to master and branch-2. > Fix or disable tests broken in branch-2 so can cut

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

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)

HBase 1.3.2-SNAPSHOT (20180113T013910Z)

A snapshot of HBase 1.3.2 is available for testing in Apache's Maven or at ​​ https://dist.apache.org/repos/dist/dev/hbase/hbase-1.3.2-SNAPSHOT/ . This snapshot was generated from the git SHA b6f4f511a6 . ​The compatibility report with respect to the previous release can be found at ​

Re: [VOTE] The fourth hbase-2.0.0-beta-1 Release Candidate is available for download

+1 Checked sig and hash. Downloaded locally. Undid and loaded data. Logs look good. Put on cluster. Picks up old data fine. Nothing odd in logs (too much logging but that is another story). St.Ack On Fri, Jan 12, 2018 at 8:48 PM, Stack wrote: > The fourth release candidate

[jira] [Created] (HBASE-19790) Fix compatibility break in 1.3.2-SNAPSHOT

Andrew Purtell created HBASE-19790: -- Summary: Fix compatibility break in 1.3.2-SNAPSHOT Key: HBASE-19790 URL: https://issues.apache.org/jira/browse/HBASE-19790 Project: HBase Issue Type:

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

[DISCUSS] Purge hbase-archetypes?

Anyone using it? As far as I know it goes unsupported (anyone interested in this project?). Building a release takes two hours, one hour of which is archetype machinations, so its not my favorite module these times. Purge it from hbase? St.Ack

Re: Going to roll 1.3.2 RC in next few weeks

I'm going to make a snapshot of 1.3.2-SNAPSHOT available. On Fri, Jan 5, 2018 at 9:37 AM, Andrew Purtell wrote: > Ok. Great! > > Will revisit this next month. > > On Jan 5, 2018, at 9:35 AM, Francis Christopher Liu > wrote: > > I'm interested in

[VOTE] The fourth hbase-2.0.0-beta-1 Release Candidate is available for download

The fourth release candidate for HBase 2.0.0-beta-1 is up at: https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0-beta-1-RC3/ Maven artifacts are available from a staging directory here: https://repository.apache.org/content/repositories/orgapachehbase-1193 All was signed with my key

[jira] [Resolved] (HBASE-19752) RSGroupBasedLoadBalancer#getMisplacedRegions() should handle the case where rs group cannot be determined

[ https://issues.apache.org/jira/browse/HBASE-19752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu resolved HBASE-19752. Resolution: Fixed > RSGroupBasedLoadBalancer#getMisplacedRegions() should handle the case where > rs

HBase 1.4.1-SNAPSHOT (20180112T235345Z)

A snapshot of HBase 1.4.1 is available for testing in Apache's Maven or at https://dist.apache.org/repos/dist/dev/hbase/hbase-1.4.1-SNAPSHOT/ . This snapshot was generated from the git SHA e13e9029a1 . This is a snapshot, not an official release. These artifacts are provided for development and

[jira] [Created] (HBASE-19788) Reenable TestFavoredStochasticLoadBalancer; disabled by HBASE-19787

stack created HBASE-19788: - Summary: Reenable TestFavoredStochasticLoadBalancer; disabled by HBASE-19787 Key: HBASE-19788 URL: https://issues.apache.org/jira/browse/HBASE-19788 Project: HBase Issue

[jira] [Created] (HBASE-19785) System Regions on the Master is broken by parent HBASE-19694

stack created HBASE-19785: - Summary: System Regions on the Master is broken by parent HBASE-19694 Key: HBASE-19785 URL: https://issues.apache.org/jira/browse/HBASE-19785 Project: HBase Issue Type:

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

[jira] [Created] (HBASE-19786) acl table is created by coprocessor inside Master start procedure; broke TestJMXConnectorServer

stack created HBASE-19786: - Summary: acl table is created by coprocessor inside Master start procedure; broke TestJMXConnectorServer Key: HBASE-19786 URL: https://issues.apache.org/jira/browse/HBASE-19786

[jira] [Created] (HBASE-19789) Exclude flaky tests from nightly branch-2 runs

Appy created HBASE-19789: Summary: Exclude flaky tests from nightly branch-2 runs Key: HBASE-19789 URL: https://issues.apache.org/jira/browse/HBASE-19789 Project: HBase Issue Type: Improvement

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: [VOTE] The third hbase-2.0.0-beta-1 Release Candidate is available for download

I'm sinking this RC. Pardon the inconvenience. Appy put up this dashboard for branch-2 last night: https://builds.apache.org/view/H-L/view/HBase/job/HBase-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html There are a bunch of tests that fail always in the RC. I only realized the extent

[jira] [Reopened] (HBASE-19752) RSGroupBasedLoadBalancer#getMisplacedRegions() should handle the case where rs group cannot be determined

[ https://issues.apache.org/jira/browse/HBASE-19752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Purtell reopened HBASE-19752: Reverted from branch-1.4 due to compilation failure. Please fix and reapply. >

[jira] [Resolved] (HBASE-15042) refactor so that site materials are in the Standard Maven Place

[ https://issues.apache.org/jira/browse/HBASE-15042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Hentschel resolved HBASE-15042. --- Resolution: Fixed > refactor so that site materials are in the Standard Maven Place >

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: > > >