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

ASF GitHub Bot logged work on HDFS-15600:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 29/Sep/20 03:41
            Start Date: 29/Sep/20 03:41
    Worklog Time Spent: 10m 
      Work Description: liuml07 commented on pull request #2347:
URL: https://github.com/apache/hadoop/pull/2347#issuecomment-700407063


   I have not had a second look at the original patch regarding compatibility, 
but we can merge this patch first to make test in trunk pass.
   
   If we need to make any further changes to the original NVDIMM feature eg 
reordering, we can also update this test again.


----------------------------------------------------------------
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: 492255)
    Time Spent: 20m  (was: 10m)

> TestRouterQuota fails in trunk
> ------------------------------
>
>                 Key: HDFS-15600
>                 URL: https://issues.apache.org/jira/browse/HDFS-15600
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: rbf
>            Reporter: Ayush Saxena
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The test is failing due to addition of a new storage type {{NVDIMM}} in 
> middle.
> Ref :
> https://ci-hadoop.apache.org/job/PreCommit-HDFS-Build/204/testReport/org.apache.hadoop.hdfs.server.federation.router/TestRouterQuota/testStorageTypeQuota/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to