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

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

                Author: ASF GitHub Bot
            Created on: 19/Oct/21 08:24
            Start Date: 19/Oct/21 08:24
    Worklog Time Spent: 10m 
      Work Description: aajisaka commented on pull request #3514:
URL: https://github.com/apache/hadoop/pull/3514#issuecomment-946478448


   The patch has been merged. Closing.


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

> Fix TestViewFsTrash to use the correct homeDir.
> -----------------------------------------------
>
>                 Key: HADOOP-16532
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16532
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: test, viewfs
>    Affects Versions: 3.3.0
>            Reporter: Steve Loughran
>            Assignee: Xing Lin
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 3.4.0, 2.10.2, 3.3.2, 3.2.4
>
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> the test {{TestViewFsTrash}} uses the .Trash directory under the current 
> user's home dir so
> * fails in test setups which block writing to it (jenkins)
> * fails when users have real trash in there
> * may fail if there are parallel test runs.
> the home dir should be under some test path of the build.



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