+1 (binding)

        * Signature: ok
        * Checksum : ok
        * Rat check (1.8.0_352): ok
         - mvn clean apache-rat:check
        * Built from source (1.8.0_352): failed
         - mvn clean install  -DskipTests
        * Unit tests pass (1.8.0_352): failed
         - mvn clean package -P runAllTests
 -Dsurefire.rerunFailingTestsCount=3
         - TestShell#testRunShellTests is always failing
        * Started standalone and check UI: ok
        * tested create/put/get/scan/flush/list/disable/drop : ok
        * tested LTT : ok
         - hbase ltt -num_keys 10000 -write 10:1000:32
        * tested ITBLL : ok
         - hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList
loop 1 10 100000 ${RANDOM} 16

TestShell failure is matching the nightly
https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/ , sooner or
later HBASE-23982 may become a blocker.

-Stephen



On Tue, Jan 31, 2023 at 9:03 AM Andrew Purtell <[email protected]> wrote:

> +1 (binding)
>
>         * Signature: ok
>         * Checksum : ok
>         * Rat check (1.8.0_332): ok
>          - mvn clean apache-rat:check
>         * Built from source (1.8.0_332): ok
>          - mvn clean install  -DskipTests
>         * Unit tests pass (1.8.0_332): failed, see below
>          - mvn package -P runAllTests  -Dsurefire.rerunFailingTestsCount=3
>
> Flaky tests:
>     TestSlowLogAccessor.testHigherSlowLogs:209 Waiting timed out after
> [7,000] msec
>     TestFromClientSide3.testScanAfterDeletingSpecifiedRow:203 expected:<1>
> but was:<0>
>
>
> TestStochasticLoadBalancerRegionReplicaWithRacks.testRegionReplicationOnLargeClusterWithRacks:95
>
>
> ->BalancerTestBase.testWithClusterWithIteration:577->BalancerTestBase.assertRegionReplicaPlacement:254
>         Two or more region replicas are hosted on the same rack after
> balance
>
>
> TestBasicWALEntryStreamAsyncFSWAL>TestBasicWALEntryStream.testSizeOfLogQueue:703
>         expected:<1> but was:<2>
>
> Consistently failing tests:
>     TestShell.testRunShellTests
>
> The TestShell failure appears to be tracked by HBASE-23982 and I added my
> findings as https://s.apache.org/gvk18 .
>
>
> On Mon, Jan 30, 2023 at 5:32 AM 张铎(Duo Zhang) <[email protected]>
> wrote:
>
> > Please vote on this Apache hbase release candidate,
> > hbase-2.4.16RC0
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache hbase 2.4.16
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 2.4.16RC0:
> >
> >   https://github.com/apache/hbase/tree/2.4.16RC0
> >
> > This tag currently points to git reference
> >
> >   b91e903536bb689a01e0b25e93e9a7fe9294f100
> >
> > The release files, including signatures, digests, as well as CHANGES.md
> > and RELEASENOTES.md included in this RC can be found at:
> >
> >   https://dist.apache.org/repos/dist/dev/hbase/2.4.16RC0/
> >
> > Maven artifacts are available in a staging repository at:
> >
> >
> https://repository.apache.org/content/repositories/orgapachehbase-1510/
> >
> > Artifacts were signed with the 0x9AD2AE49 key which can be found in:
> >
> >   https://downloads.apache.org/hbase/KEYS
> >
> > To learn more about Apache hbase, please see
> >
> >   http://hbase.apache.org/
> >
> > Thanks,
> > Your HBase Release Manager
> >
>
>
> --
> Best regards,
> Andrew
>
> Unrest, ignorance distilled, nihilistic imbeciles -
>     It's what we’ve earned
> Welcome, apocalypse, what’s taken you so long?
> Bring us the fitting end that we’ve been counting on
>    - A23, Welcome, Apocalypse
>

Reply via email to