-1 Tests under hbase-rsgroup fail in setup phase. It is related to HBASE-20224, some addendums were not backported to branch-2.0 which causes the failure. I'm reopening HBASE-20224 and backport 2 missing commits.
On Fri, Apr 13, 2018 at 3:54 PM, Jean-Marc Spaggiari < jean-m...@spaggiari.org> wrote: > Exactly what I was looking for! Thanks Sean! > > 2018-04-13 9:37 GMT-04:00 Sean Busbey <bus...@apache.org>: > > > Hi JMS! > > > > Current flaky results for branch-2.0, generated today AFAICT: > > > > https://builds.apache.org/view/H-L/view/HBase/job/HBase- > > Find-Flaky-Tests-branch2.0/lastSuccessfulBuild/artifact/ > > > > you can look at the "dashboard.html" artifact for a human usable idea > > of what we think is broken. > > > > you can fetch the excludes file to get a pattern you can pass to Maven. > > > > > > On Fri, Apr 13, 2018 at 7:40 AM, Jean-Marc Spaggiari > > <jean-m...@spaggiari.org> wrote: > > > Do we have a list of tests that we know will not pass this release? > > > > > > I got those failures so far, but since I want to run multiple runs, I > > want > > > to make sure to exclude the un-stable tests. > > > > > > TestAssignmentManagerMetrics.testRITAssignmentManagerMetrics:152 > Metrics > > > Should be equal expected:<1> but was:<0> > > > TestReplicationSmallTests.testDisableEnable:198 Replication wasn't > > disabled > > > TestReplicationSmallTests.testSimplePutDelete:168-> > TestReplicationBase. > > runSimplePutDeleteTest:266 > > > Waited too much time for put replication > > > TestClientOperationTimeout.setUp:99 ยป SocketTimeout callTimeout=500, > > > callDurat... > > > > > > Thanks, > > > > > > JMS > > > > > > > > > 2018-04-13 0:19 GMT-04:00 Yu Li <car...@gmail.com>: > > > > > >> bq. I'd imagine that if the difference were large, then yes, it should > > >> be a blocker > > >> -- or we as a community can decide to work on it in a follow-on > release > > >> making perf a priority (say, 2.1.0). > > >> I see, thanks for the clarification boss, makes sense. > > >> > > >> Best Regards, > > >> Yu > > >> > > >> On 13 April 2018 at 06:02, Stack <st...@duboce.net> wrote: > > >> > > >> > On Thu, Apr 12, 2018 at 1:47 PM, Stack <st...@duboce.net> wrote: > > >> > > > >> > > On Tue, Apr 10, 2018 at 2:50 PM, Sean Busbey <bus...@apache.org> > > >> wrote: > > >> > > > > >> > >> no compat report in the RC directory. does that mean we won't > have > > one > > >> > >> in the dist area? > > >> > >> > > >> > >> > > >> > >> not a blocker; we've been inconsistent on it in prior releases, > but > > >> > >> the trend seemed to be towards including it. > > >> > >> > > >> > >> > > >> > > > > >> > > HBASE-18622 has current state of compatibility compare. Let me do > a > > new > > >> > > run and add it to the RC dir. > > >> > > > > >> > > > >> > I just added > > >> > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/ > > >> > compat-check-v1.2.6-v2.0.0.report.html > > >> > > > >> > Thanks, > > >> > S > > >> > > > >> > > > >> > > > >> > > St.Ack > > >> > > > > >> > > > > >> > > > > >> > >> > > >> > >> On Tue, Apr 10, 2018 at 3:47 PM, Stack <st...@duboce.net> wrote: > > >> > >> > The first release candidate for Apache HBase 2.0.0 is available > > for > > >> > >> > downloading and testing. > > >> > >> > > > >> > >> > Artifacts are available here: > > >> > >> > > > >> > >> > https://dist.apache.org/repos/dist/dev/hbase/hbase-2.0.0RC0/ > > >> > >> > > > >> > >> > Maven artifacts are available in the staging repository at: > > >> > >> > > > >> > >> > https://repository.apache.org/content/repositories/ > > >> > orgapachehbase-1209 > > >> > >> > > > >> > >> > All artifacts are signed with my signing key 8ACC93D2, which is > > also > > >> > >> > in the project KEYS file at > > >> > >> > > > >> > >> > http://www.apache.org/dist/hbase/KEYS > > >> > >> > > > >> > >> > These artifacts were tagged 2.0.0RC0 at > > >> > >> > hash 011dd2dae33456b3a2bcc2513e9fdd29de23be46 > > >> > >> > > > >> > >> > Please review 'Upgrading from 1.x to 2.x' in the bundled HBase > > 2.0.0 > > >> > >> > Reference Guide before installing or upgrading for a list of > > >> > >> > incompatibilities, major changes, and notable new features. Be > > aware > > >> > >> that > > >> > >> > according to our adopted Semantic Versioning guidelines[1], > we've > > >> > allow > > >> > >> > ourselves to make breaking changes in this major version > release. > > >> For > > >> > >> > example, Coprocessors will need to be recast to fit more > > constrained > > >> > CP > > >> > >> > APIs and a rolling upgrade of an hbase-1.x install to hbase-2.x > > >> > without > > >> > >> > downtime is (currently) not possible. That said, a bunch of > > effort > > >> has > > >> > >> been > > >> > >> > expended mitigating differences; a hbase-1.x client can perform > > DML > > >> > >> against > > >> > >> > an hbase-2 cluster. > > >> > >> > > > >> > >> > For the full list of ~6k issues addressed, see [2]. There are > > also > > >> > >> > CHANGES.md and RELEASENOTES.md in the root directory of the > > source > > >> > >> tarball. > > >> > >> > > > >> > >> > Please take a few minutes to verify the release and vote on > > >> releasing > > >> > >> it: > > >> > >> > > > >> > >> > [ ] +1 Release this package as Apache HBase 2.0.0 > > >> > >> > [ ] +0 no opinion > > >> > >> > [ ] -1 Do not release this package because... > > >> > >> > > > >> > >> > This VOTE will run for one week and close Tuesday, April 17, > > 2018 @ > > >> > >> 13:00 > > >> > >> > PST. > > >> > >> > > > >> > >> > Thanks to the myriad who have helped out with this release, > > >> > >> > Your 2.0.0 Release Manager > > >> > >> > > > >> > >> > 1. http://hbase.apache.org/2.0/book.html#hbase.versioning. > post10 > > >> > >> > 2. https://s.apache.org/zwS9 > > >> > >> > > >> > > > > >> > > > > >> > > > >> > > >
