[
https://issues.apache.org/jira/browse/HBASE-27360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602620#comment-17602620
]
Hudson commented on HBASE-27360:
--------------------------------
Results for branch branch-2
[build #641 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/641/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/641/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/641/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/641/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/641/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> The trace related assertions are flaky for async client tests
> -------------------------------------------------------------
>
> Key: HBASE-27360
> URL: https://issues.apache.org/jira/browse/HBASE-27360
> Project: HBase
> Issue Type: Bug
> Components: test, tracing
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 2.6.0, 2.5.1, 3.0.0-alpha-4
>
>
> https://ci-hbase.apache.org/job/HBase-Flaky-Tests/job/master/4167/testReport/junit/org.apache.hadoop.hbase.client/TestAsyncTableScanner/testScanWrongColumnFamily_0__table_raw__scan_normal_/
> The failure message is kinda unreadable... I guess the problem is we do not
> wait enough time as the completion of the span can be executed concurrently
> with normal scan operation.
> And also I saw this in the test code
> {code}
> // RawAsyncTableImpl never invokes the callback to `onScanMetricsCreated`
> -- bug?
> {code}
> This is not a bug as you need to manually enable scan metrics by calling
> Scan.setScanMetricsEnabled(true).
> Let me also fix this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
