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

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

                Author: ASF GitHub Bot
            Created on: 26/Apr/19 06:05
            Start Date: 26/Apr/19 06:05
    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-486937246
 
 
   @cjjnjust Sorry I was not very clear on the previous comment. 
   
   conf.get() without a default value will return null for schemaFileType when 
the key is not defined, which is the case for some tests. This will cause NPE 
but was caught by catch (Throwable e) and rethrow as RTE with log message "Fail 
to load schema file...".
 
----------------------------------------------------------------
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: 233279)
    Time Spent: 1h 20m  (was: 1h 10m)

> 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: 1h 20m
>  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