[
https://issues.apache.org/jira/browse/HBASE-23977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063762#comment-17063762
]
Hudson commented on HBASE-23977:
--------------------------------
Results for branch branch-2
[build #2559 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2559/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2559//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2559//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2559//JDK8_Nightly_Build_Report_(Hadoop3)/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2559//JDK11_Nightly_Build_Report/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 2. [see log for
details|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2559//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> [Flakey Tests]
> TestSlowLogRecorder.testOnlieSlowLogConsumption:178->confirmPayloadParams:97
> expected:<client_1[0]> but was:<client_1[4]>
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-23977
> URL: https://issues.apache.org/jira/browse/HBASE-23977
> Project: HBase
> Issue Type: Bug
> Components: test
> Affects Versions: 3.0.0, 2.3.0
> Reporter: Michael Stack
> Assignee: Viraj Jasani
> Priority: Major
> Labels: flaky-test
> Fix For: 3.0.0, 2.3.0, 2.4.0
>
>
> I see this occasionally on a linux vm. [~vjasani] .. you might have an idea
> why this is going on (this is your test I believe and a recent addition). If
> you have stuff I can try, shout.
> Here is fail:
> {code}
> org.junit.ComparisonFailure: expected:<client_1[0]> but was:<client_1[4]>
> at
> org.apache.hadoop.hbase.regionserver.slowlog.TestSlowLogRecorder.confirmPayloadParams(TestSlowLogRecorder.java:97)
> at
> org.apache.hadoop.hbase.regionserver.slowlog.TestSlowLogRecorder.testOnlieSlowLogConsumption(TestSlowLogRecorder.java:178)
> {code}
> Here is log:
> {code}
> 2020-03-12 17:02:06,266 INFO [Time-limited test] hbase.ResourceChecker(179):
> after:
> regionserver.slowlog.TestSlowLogRecorder#testOnlineSlowLogWithDisableConfig
> Thread=7 (was 7), OpenFileDescriptor=226 (was 226),
> MaxFileDescriptor=131072 (was 131072), SystemLoadAverage=353 (was 353),
> ProcessCount=195 (was 195), AvailableMemoryMB=7037 (was 7027) -
> AvailableMemoryMB LEAK? -
> 2020-03-12 17:02:06,281 INFO [Time-limited test]
> hbase.ResourceChecker(151): before:
> regionserver.slowlog.TestSlowLogRecorder#testOnlieSlowLogConsumption
> Thread=7, OpenFileDescriptor=226, MaxFileDescriptor=131072,
> SystemLoadAverage=353, ProcessCount=195, AvailableMemoryMB=7036
> 2020-03-12 17:02:06,317 DEBUG [Time-limited test]
> slowlog.TestSlowLogRecorder(111): Initially ringbuffer of Slow Log records is
> empty
> 2020-03-12 17:02:06,326 INFO [Time-limited test] hbase.Waiter(183): Waiting
> up to [3,000] milli-secs(wait.for.ratio=[1])
> 2020-03-12 17:02:06,528 INFO [Time-limited test] hbase.Waiter(183): Waiting
> up to [3,000] milli-secs(wait.for.ratio=[1])
> 2020-03-12 17:02:06,630 INFO [Time-limited test] hbase.Waiter(183): Waiting
> up to [3,000] milli-secs(wait.for.ratio=[1])
> 2020-03-12 17:02:06,732 INFO [Time-limited test] hbase.Waiter(183): Waiting
> up to [3,000] milli-secs(wait.for.ratio=[1])
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
