[ 
https://issues.apache.org/jira/browse/HDDS-1450?focusedWorklogId=231452&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-231452
 ]

ASF GitHub Bot logged work on HDDS-1450:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 23/Apr/19 15:22
            Start Date: 23/Apr/19 15:22
    Worklog Time Spent: 10m 
      Work Description: xiaoyuyao commented on issue #757: HDDS-1450. Fix 
nightly run failures after HDDS-976. Contributed by Xi…
URL: https://github.com/apache/hadoop/pull/757#issuecomment-485850124
 
 
   bq. Does this fix the nightly build? It seems not fix "the good.xml file not 
found" issue, how does it work?
   
   The reason of the failure I guess is that 
ozone.scm.network.topology.schema.file.type does not have a default value. By 
removing this key, init() loading will be based on file extension directly. It 
seems to be working based on the result here: 
https://ci.anzix.net/job/ozone/16691/testReport/
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 231452)
    Time Spent: 50m  (was: 40m)

> Fix nightly run failures after HDDS-976
> ---------------------------------------
>
>                 Key: HDDS-1450
>                 URL: https://issues.apache.org/jira/browse/HDDS-1450
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Xiaoyu Yao
>            Assignee: Xiaoyu Yao
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> [https://ci.anzix.net/job/ozone-nightly/72/testReport/]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to