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

ASF GitHub Bot logged work on HADOOP-17936:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 24/Sep/21 18:51
            Start Date: 24/Sep/21 18:51
    Worklog Time Spent: 10m 
      Work Description: sunchao commented on pull request #3478:
URL: https://github.com/apache/hadoop/pull/3478#issuecomment-926850295


   @steveloughran good question. it's not because we still have HADOOP-16878 / 
#1857 in the trunk so the test is passing there. Should we revert it there too? 
because the JIRA is re-opened.


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

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

    Worklog Id:     (was: 655047)
    Time Spent: 40m  (was: 0.5h)

> Fix test failure after reverting HADOOP-16878 from branch-3.3
> -------------------------------------------------------------
>
>                 Key: HADOOP-17936
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17936
>             Project: Hadoop Common
>          Issue Type: Test
>            Reporter: Chao Sun
>            Assignee: Chao Sun
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.3.2
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> After reverting HADOOP-16878 from branch-3.3, test 
> {{TestLocalFSCopyFromLocal.testDestinationFileIsToParentDirectory}} started 
> to fail because it expects an exception but the copying succeeded.



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