[ 
https://issues.apache.org/jira/browse/TEZ-3993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16622770#comment-16622770
 ] 

TezQA commented on TEZ-3993:
----------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12940670/TEZ-3993.001.patch
  against master revision 381dac0.

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 3.0.1) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in :
                   org.apache.tez.mapreduce.TestMRRJobsDAGApi
                  org.apache.tez.test.TestExceptionPropagation
                  org.apache.tez.mapreduce.TestMRRJobs
                  org.apache.tez.test.TestDAGRecovery2
                  org.apache.tez.test.TestDAGRecovery
                  org.apache.tez.test.TestAMRecovery
                  org.apache.tez.test.TestTezJobs
                  org.apache.tez.test.TestPipelinedShuffle
                  org.apache.tez.test.TestFaultTolerance
                  org.apache.tez.test.TestRecovery
                  org.apache.tez.test.TestSecureShuffle
                  org.apache.tez.tests.TestExternalTezServicesErrors
                  org.apache.tez.tests.TestExternalTezServices
                  org.apache.tez.analyzer.TestAnalyzer
                  
org.apache.tez.dag.history.logging.ats.TestATSHistoryWithMiniCluster
                  org.apache.tez.history.TestHistoryParser
                  org.apache.tez.dag.history.ats.acls.TestATSHistoryV15
                  org.apache.tez.auxservices.TestShuffleHandlerJobs
                  org.apache.tez.dag.history.ats.acls.TestATSHistoryWithACLs
                  org.apache.tez.client.TestTezClientUtils
                  org.apache.tez.common.TestTezCommonUtils

                                      The following test timeouts occurred in :
 org.apache.tez.dag.app.rm.TestTaskScheduler

Test results: 
https://builds.apache.org/job/PreCommit-TEZ-Build/2925//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2925//console

This message is automatically generated.


> Tez fails to parse windows file paths in local mode
> ---------------------------------------------------
>
>                 Key: TEZ-3993
>                 URL: https://issues.apache.org/jira/browse/TEZ-3993
>             Project: Apache Tez
>          Issue Type: Bug
>            Reporter: Jonathan Eagles
>            Assignee: Jonathan Eagles
>            Priority: Major
>         Attachments: TEZ-3993.001.patch
>
>
> TezLocalCacheManager tries to generate symlinks to files that it puts in the 
> local cache, but the code that it uses to construct the path names is not 
> safe on Windows and causes bad file names to be constructed when run in a 
> Windows environment. On Windows, a path like file:/c:/path/to/my/file should 
> be legal and transform to c:\path\to\my\file, but with the invalid construct, 
> it turns into the illegal value /c:/path/to/my/file instead.
> In TezLocalCacheManager, there is code that does
> {code}
> private boolean createSymlink(Path target, Path link) throws IOException {
>     LOG.info("Creating symlink: {} <- {}", target, link);
>     String targetPath = target.toUri().getPath();
>     String linkPath = link.toUri().getPath();
> {code}
> It looks like there are several other places in the Tez code that also use 
> the Path.toUri().getPath() construct that probably also need to be fixed in 
> order to work correctly on Windows.
> The construct Path.toUri().getPath() doesn't handle windows directories 
> correctly. The Java File class understands how to do this correctly, so this 
> should really be replaced by
> {code}
> private boolean createSymlink(Path target, Path link) throws IOException {
>     LOG.info("Creating symlink: {} <- {}", target, link);
>     String targetPath = new File(target.toUri()).getCanonicalPath();
>     String linkPath = new File(link.toUri()).getCanonicalPath();
> {code}
> {code}
> 2018-09-19T16:32:53,287 ERROR [LocalContainerLauncher-SubTaskRunner] 
> org.apache.tez.dag.app.launcher.LocalContainerLauncher - TezSubTaskRunner 
> failed due to exception
> java.nio.file.InvalidPathException: Illegal char <:> at index 2: 
> /C:/Users/...fullpath
>         at sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)
>         at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)
>         at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
>         at sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)
>         at sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)
>         at java.nio.file.Paths.get(Paths.java:84)
>         at 
> org.apache.tez.dag.app.launcher.TezLocalCacheManager.createSymlink(TezLocalCacheManager.java:173)
>         at 
> org.apache.tez.dag.app.launcher.TezLocalCacheManager.localize(TezLocalCacheManager.java:126)
>         at 
> org.apache.tez.dag.app.launcher.LocalContainerLauncher.launch(LocalContainerLauncher.java:263)
>         at 
> org.apache.tez.dag.app.launcher.LocalContainerLauncher.access$300(LocalContainerLauncher.java:82)
>         at 
> org.apache.tez.dag.app.launcher.LocalContainerLauncher$TezSubTaskRunner.run(LocalContainerLauncher.java:207)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to