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

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

                Author: ASF GitHub Bot
            Created on: 07/Feb/21 01:49
            Start Date: 07/Feb/21 01:49
    Worklog Time Spent: 10m 
      Work Description: LeonGao91 commented on pull request #2679:
URL: https://github.com/apache/hadoop/pull/2679#issuecomment-774574666


   @sodonnel Thanks for the review! Fixed checkstyle


----------------------------------------------------------------
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: 549185)
    Time Spent: 1h 10m  (was: 1h)

> Fix TestFsDatasetImpl.testReadLockCanBeDisabledByConfig
> -------------------------------------------------------
>
>                 Key: HDFS-15818
>                 URL: https://issues.apache.org/jira/browse/HDFS-15818
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: test
>            Reporter: Leon Gao
>            Assignee: Leon Gao
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Current TestFsDatasetImpl.testReadLockCanBeDisabledByConfig is incorrect:
> 1) Test fails intermittently as holder can acquire lock first
> [https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2666/1/testReport/]
>  
> 2) Test passes regardless of the setting of 
> DFS_DATANODE_LOCK_READ_WRITE_ENABLED_KEY



--
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