You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/11/03 13:41:01 UTC
[jira] [Updated] (HDDS-4418) TestContainerMetrics is flaky
[ https://issues.apache.org/jira/browse/HDDS-4418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HDDS-4418:
---------------------------------
Labels: pull-request-available (was: )
> TestContainerMetrics is flaky
> -----------------------------
>
> Key: HDDS-4418
> URL: https://issues.apache.org/jira/browse/HDDS-4418
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: test
> Reporter: Marton Elek
> Assignee: Marton Elek
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.1.0
>
>
> TestContainerMetrics is flaky since HDDS-4359. Failed in following master builds:
> {code}
> 2020/10/26/3569/it-ozone/hadoop-ozone/integration-test/TEST-org.apache.hadoop.ozone.container.metrics.TestContainerMetrics.xml
> 2020/10/27/3581/it-ozone/hadoop-ozone/integration-test/TEST-org.apache.hadoop.ozone.container.metrics.TestContainerMetrics.xml
> 2020/10/28/3591/it-ozone/hadoop-ozone/integration-test/TEST-org.apache.hadoop.ozone.container.metrics.TestContainerMetrics.xml
> 2020/10/29/3619/it-ozone/hadoop-ozone/integration-test/TEST-org.apache.hadoop.ozone.container.metrics.TestContainerMetrics.xml
> 2020/10/30/3628/it-ozone/hadoop-ozone/integration-test/TEST-org.apache.hadoop.ozone.container.metrics.TestContainerMetrics.xml
> 2020/10/30/3642/it-ozone/hadoop-ozone/integration-test/TEST-org.apache.hadoop.ozone.container.metrics.TestContainerMetrics.xml
> 2020/10/31/3650/it-ozone/hadoop-ozone/integration-test/TEST-org.apache.hadoop.ozone.container.metrics.TestContainerMetrics.xml
> 2020/10/31/3654/it-ozone/hadoop-ozone/integration-test/TEST-org.apache.hadoop.ozone.container.metrics.TestContainerMetrics.xml
> {code}
> Some of the added assertions couldn't be guaranteed all the time:
> {code}
> // ReadTime and WriteTime vary from run to run, only checking non-zero
> Assert.assertNotEquals(0L, getLongCounter("ReadTime", volumeIOMetrics));
> Assert.assertNotEquals(0L, getLongCounter("WriteTime", volumeIOMetrics));
> {code}
> In very lucky case the read/write time can be zero.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org