You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Marton Elek (Jira)" <ji...@apache.org> on 2020/04/28 13:49:00 UTC
[jira] [Updated] (HDDS-3504) Topology related acceptance test is
intermittent
[ https://issues.apache.org/jira/browse/HDDS-3504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marton Elek updated HDDS-3504:
------------------------------
Description:
It's failed multiple times on master and PRs. See the archive of the builds results at: https://github.com/elek/ozone-build-results
I am disabling it to avoid flaky runs, but we need to fix and re-enable it.
{code}
./find-first.sh "Test timeout 5 minutes exceeded." --include="robot-ozone-topology-ozone-topology-basic-scm.xml"
2020/04/17/789/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<msg timestamp="20200417 18:06:32.549" level="FAIL">Test timeout 5 minutes exceeded.</msg>
2020/04/17/789/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<status status="FAIL" starttime="20200417 18:01:32.547" endtime="20200417 18:06:32.550" critical="yes">Test timeout 5 minutes exceeded.</status>
2020/04/17/791/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<msg timestamp="20200417 18:55:52.135" level="FAIL">Test timeout 5 minutes exceeded.</msg>
2020/04/17/791/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<status status="FAIL" starttime="20200417 18:50:52.134" endtime="20200417 18:55:52.135" critical="yes">Test timeout 5 minutes exceeded.</status>
2020/04/20/792/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<msg timestamp="20200420 12:16:47.410" level="FAIL">Test timeout 5 minutes exceeded.</msg>
2020/04/20/792/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<status status="FAIL" starttime="20200420 12:11:47.409" endtime="20200420 12:16:47.411" critical="yes">Test timeout 5 minutes exceeded.</status>
2020/04/21/803/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<msg timestamp="20200422 00:10:32.971" level="FAIL">Test timeout 5 minutes exceeded.</msg>
2020/04/21/803/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<status status="FAIL" starttime="20200422 00:05:32.970" endtime="20200422 00:10:32.972" critical="yes">Test timeout 5 minutes exceeded.</status>
2020/04/27/830/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<msg timestamp="20200427 22:05:52.823" level="FAIL">Test timeout 5 minutes exceeded.</msg>
2020/04/27/830/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<status status="FAIL" starttime="20200427 22:00:52.822" endtime="20200427 22:05:52.824" critical="yes">Test timeout 5 minutes exceeded.</status>
First failed commit: 3bb5838196536f2ea4ac1ab4dcd0bc53ae97f7e0
{code}
was:
It's failed multiple times on master and PRs. See the archive of the builds results at: https://github.com/elek/ozone-build-results
I am disabling it to avoid flaky runs, but we need to fix and re-enable it.
{code}
./find-first.sh "Test timeout 5 minutes exceeded." --include="robot-ozone-topology-ozone-topology-basic-scm.xml"
2020/04/17/789/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<msg timestamp="20200417 18:06:32.549" level="FAIL">Test timeout 5 minutes exceeded.</msg>
2020/04/17/789/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<status status="FAIL" starttime="20200417 18:01:32.547" endtime="20200417 18:06:32.550" critical="yes">Test timeout 5 minutes exceeded.</status>
2020/04/17/791/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<msg timestamp="20200417 18:55:52.135" level="FAIL">Test timeout 5 minutes exceeded.</msg>
2020/04/17/791/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<status status="FAIL" starttime="20200417 18:50:52.134" endtime="20200417 18:55:52.135" critical="yes">Test timeout 5 minutes exceeded.</status>
2020/04/20/792/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<msg timestamp="20200420 12:16:47.410" level="FAIL">Test timeout 5 minutes exceeded.</msg>
2020/04/20/792/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<status status="FAIL" starttime="20200420 12:11:47.409" endtime="20200420 12:16:47.411" critical="yes">Test timeout 5 minutes exceeded.</status>
2020/04/21/803/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<msg timestamp="20200422 00:10:32.971" level="FAIL">Test timeout 5 minutes exceeded.</msg>
2020/04/21/803/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<status status="FAIL" starttime="20200422 00:05:32.970" endtime="20200422 00:10:32.972" critical="yes">Test timeout 5 minutes exceeded.</status>
2020/04/27/830/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<msg timestamp="20200427 22:05:52.823" level="FAIL">Test timeout 5 minutes exceeded.</msg>
2020/04/27/830/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<status status="FAIL" starttime="20200427 22:00:52.822" endtime="20200427 22:05:52.824" critical="yes">Test timeout 5 minutes exceeded.</status>
First failed commit: 3bb5838196536f2ea4ac1ab4dcd0bc53ae97f7e0
{code}
* 2020-04-17 09:42:19 -0700 3bb583819 E - Update grpc/netty d
> Topology related acceptance test is intermittent
> ------------------------------------------------
>
> Key: HDDS-3504
> URL: https://issues.apache.org/jira/browse/HDDS-3504
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Marton Elek
> Priority: Critical
>
> It's failed multiple times on master and PRs. See the archive of the builds results at: https://github.com/elek/ozone-build-results
> I am disabling it to avoid flaky runs, but we need to fix and re-enable it.
> {code}
> ./find-first.sh "Test timeout 5 minutes exceeded." --include="robot-ozone-topology-ozone-topology-basic-scm.xml"
> 2020/04/17/789/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<msg timestamp="20200417 18:06:32.549" level="FAIL">Test timeout 5 minutes exceeded.</msg>
> 2020/04/17/789/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<status status="FAIL" starttime="20200417 18:01:32.547" endtime="20200417 18:06:32.550" critical="yes">Test timeout 5 minutes exceeded.</status>
> 2020/04/17/791/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<msg timestamp="20200417 18:55:52.135" level="FAIL">Test timeout 5 minutes exceeded.</msg>
> 2020/04/17/791/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<status status="FAIL" starttime="20200417 18:50:52.134" endtime="20200417 18:55:52.135" critical="yes">Test timeout 5 minutes exceeded.</status>
> 2020/04/20/792/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<msg timestamp="20200420 12:16:47.410" level="FAIL">Test timeout 5 minutes exceeded.</msg>
> 2020/04/20/792/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<status status="FAIL" starttime="20200420 12:11:47.409" endtime="20200420 12:16:47.411" critical="yes">Test timeout 5 minutes exceeded.</status>
> 2020/04/21/803/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<msg timestamp="20200422 00:10:32.971" level="FAIL">Test timeout 5 minutes exceeded.</msg>
> 2020/04/21/803/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<status status="FAIL" starttime="20200422 00:05:32.970" endtime="20200422 00:10:32.972" critical="yes">Test timeout 5 minutes exceeded.</status>
> 2020/04/27/830/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<msg timestamp="20200427 22:05:52.823" level="FAIL">Test timeout 5 minutes exceeded.</msg>
> 2020/04/27/830/acceptance/robot-ozone-topology-ozone-topology-basic-scm.xml:<status status="FAIL" starttime="20200427 22:00:52.822" endtime="20200427 22:05:52.824" critical="yes">Test timeout 5 minutes exceeded.</status>
> First failed commit: 3bb5838196536f2ea4ac1ab4dcd0bc53ae97f7e0
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org