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

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

                Author: ASF GitHub Bot
            Created on: 03/Oct/21 14:31
            Start Date: 03/Oct/21 14:31
    Worklog Time Spent: 10m 
      Work Description: xinglin opened a new pull request #3514:
URL: https://github.com/apache/hadoop/pull/3514


   Fixed the homeDir issue reported in HADOOP-16532. We are finally able to 
pass this test for ViewFS.
   
   


-- 
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: 659335)
    Remaining Estimate: 0h
            Time Spent: 10m

> TestViewFsTrash uses home directory of real fs; brittle
> -------------------------------------------------------
>
>                 Key: HADOOP-16532
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16532
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs, test
>    Affects Versions: 3.3.0
>            Reporter: Steve Loughran
>            Priority: Minor
>          Time Spent: 10m
>  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