[
https://issues.apache.org/jira/browse/HDFS-15862?focusedWorklogId=558415&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-558415
]
ASF GitHub Bot logged work on HDFS-15862:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 26/Feb/21 06:54
Start Date: 26/Feb/21 06:54
Worklog Time Spent: 10m
Work Description: lzx404243 opened a new pull request #2724:
URL: https://github.com/apache/hadoop/pull/2724
The test
`org.apache.hadoop.hdfs.nfs.nfs3.TestViewfsWithNfs3.testNfsRenameSingleNN` is
not idempotent and fails if run twice in the same JVM, because it pollutes
state shared among tests. It may be good to clean this state pollution so that
some other tests do not fail in the future due to the shared state polluted by
this test.
### Details
Running `TestViewfsWithNfs3.testNfsRenameSingleNN` twice would result in the
second run failing with the a NullPointer exception:
```
[ERROR] Errors:
[ERROR] TestViewfsWithNfs3.testNfsRenameSingleNN:317 NullPointer
```
The reason for this is that the `/user1/renameSingleNN` file is created in
`setup()`, but gets renamed in`testNfsRenameSingleNN`. When the second run of
`testNfsRenameSingleNN` tries to get info of the file by its original name, it
returns a NullPointer since the file no longer exists.
The fix for this is to rename the file back to the original when the test is
done.
With the proposed fix, the test does not pollute the shared state (and
passes when run twice in the same JVM).
Link to JIRA issue: https://issues.apache.org/jira/browse/HDFS-15862
----------------------------------------------------------------
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: 558415)
Remaining Estimate: 0h
Time Spent: 10m
> Rename file back to original in TestViewfsWithNfs3.testNfsRenameSingleNN
> ------------------------------------------------------------------------
>
> Key: HDFS-15862
> URL: https://issues.apache.org/jira/browse/HDFS-15862
> Project: Hadoop HDFS
> Issue Type: Test
> Reporter: Zhengxi Li
> Assignee: Zhengxi Li
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The
> 'org.apache.hadoop.hdfs.nfs.nfs3.TestViewfsWithNfs3.testNfsRenameSingleNN'
> test is not idempotent and fails if run twice in the same JVM, because it
> pollutes state shared among tests. It may be good to clean this state
> pollution so that some other tests do not fail in the future due to the
> shared state polluted by this test.
> Running {{TestViewfsWithNfs3.testNfsRenameSingleNN}} twice would result in
> the second run failing with a NullPointer exception:
> {noformat}
> [ERROR] Errors:
> [ERROR] TestViewfsWithNfs3.testNfsRenameSingleNN:317 NullPointer
> {noformat}
> The reason for this is that the {{/user1/renameSingleNN}} file is created in
> {{setup()}}, but gets renamed in {{testNfsRenameSingl{{eNN}}}}. When the
> second run of {{testNfsRenameSingleNN}} tries to get info of the file by its
> original name, it returns a NullPointer since the file no longer exists.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
