[
https://issues.apache.org/jira/browse/FLINK-16394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321405#comment-17321405
]
Flink Jira Bot commented on FLINK-16394:
----------------------------------------
This issue and all of its Sub-Tasks have not been updated for 180 days. So, it
has been labeled "stale-minor". If you are still affected by this bug or are
still interested in this issue, please give an update and remove the label. In
7 days the issue will be closed automatically.
> LocalFileSystemTest.testRenameFileWithNoAccess failed when using root to
> execute mvn test on Linux system
> ---------------------------------------------------------------------------------------------------------
>
> Key: FLINK-16394
> URL: https://issues.apache.org/jira/browse/FLINK-16394
> Project: Flink
> Issue Type: Bug
> Components: FileSystems, Tests
> Affects Versions: 1.10.0
> Reporter: Peidian Li
> Priority: Minor
> Labels: stale-minor
>
> {code:java}
> [INFO] Running org.apache.flink.core.plugin.DirectoryBasedPluginFinderTest
> [ERROR] Tests run: 8, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.268
> s <<< FAILURE! - in org.apache.flink.core.fs.local.LocalFileSystemTest
> [ERROR]
> testRenameFileWithNoAccess(org.apache.flink.core.fs.local.LocalFileSystemTest)
> Time elapsed: 0.032 s <<< FAILURE!
> java.lang.AssertionError
> at
> org.apache.flink.core.fs.local.LocalFileSystemTest.testRenameFileWithNoAccess(LocalFileSystemTest.java:294)
> [ERROR] Tests run: 7, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 0.598
> s <<< FAILURE! - in org.apache.flink.util.FileUtilsTest
> [ERROR] testDeleteDirectory(org.apache.flink.util.FileUtilsTest) Time
> elapsed: 0.002 s <<< FAILURE!
> java.lang.AssertionError: this should fail with an exception
> at
> org.apache.flink.util.FileUtilsTest.testDeleteDirectory(FileUtilsTest.java:169)
> {code}
> I think it's similar to the problem of FLINK-2198
> {{File.setWritable()}} does not work on Linux when using root.
> When I use gitlab Ci, I found this problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
