[
https://issues.apache.org/jira/browse/HDDS-17081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-17081:
----------------------------------
Labels: pull-request-available (was: )
> Intermittent failure in
> TestReplicationSupervisor.testReconciliationTaskMetrics
> -------------------------------------------------------------------------------
>
> Key: HDDS-17081
> URL: https://issues.apache.org/jira/browse/HDDS-17081
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: test
> Reporter: Jheng-Sing Chen
> Assignee: Jheng-Sing Chen
> Priority: Major
> Labels: pull-request-available
>
> *Description*
> The following intermittent failure was observed:
> {{2026-10-16T00:11:09.2136973Z [INFO] Tests run: 2, Failures: 0, Errors: 0,
> Skipped: 0, Time elapsed: 2.224 s -- in
> org.apache.hadoop.ozone.container.replication.TestGrpcReplicationService
> 2026-10-16T00:11:10.2511131Z [INFO] Running
> org.apache.hadoop.ozone.container.replication.TestReplicationSupervisor
> 2026-10-16T00:11:10.5617285Z OpenJDK 64-Bit Server VM warning: Sharing is
> only supported for boot loader classes because bootstrap classpath has been
> appended
> 2026-10-16T00:11:23.0044901Z [ERROR] Tests run: 54, Failures: 1, Errors: 0,
> Skipped: 0, Time elapsed: 12.74 s <<< FAILURE! -- in
> org.apache.hadoop.ozone.container.replication.TestReplicationSupervisor
> 2026-10-16T00:11:23.0073757Z [ERROR]
> org.apache.hadoop.ozone.container.replication.TestReplicationSupervisor.testReconciliationTaskMetrics(ContainerLayoutVersion)[2]
> -- Time elapsed: 0.035 s <<< FAILURE!
> 2026-10-16T00:11:23.0103032Z org.opentest4j.AssertionFailedError: expected:
> <true> but was: <false>
> ...
> 2026-10-16T00:11:23.0162510Z at
> org.apache.hadoop.ozone.container.replication.TestReplicationSupervisor.testReconciliationTaskMetrics(TestReplicationSupervisor.java:554)}}
> The failed assertion requires reconciliation-task latency to be greater than
> zero. However, the test uses a direct executor and mocked dependencies, while
> latency is recorded in integer milliseconds. A reconciliation task can
> therefore complete within the same millisecond and correctly report {{{}0
> ms{}}}.
> This is a timing-dependent test failure rather than a production-functional
> issue. Remove the positive latency assertions and retain the request,
> success, failure, and timeout metric assertions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
