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

Chris Nauroth commented on HADOOP-11984:
----------------------------------------

Ah-ha!  There is our root cause:

{code}
     [exec] Running mkdir test.build.data: 
/home/jenkins/jenkins-slave/workspace/PreCommit-HADOOP-Build/hadoop-common-project/hadoop-common/target/test/data/{1..4}
 test.build.dir: 
/home/jenkins/jenkins-slave/workspace/PreCommit-HADOOP-Build/hadoop-common-project/hadoop-common/target/test-dir/{1..4}
 hadoop.tmp.dir: 
/home/jenkins/jenkins-slave/workspace/PreCommit-HADOOP-Build/hadoop-common-project/hadoop-common/target/test/{1..4}
{code}

It looks like Jenkins (and only Jenkins so far) is running a shell that isn't 
expanding {{\{1..4\}}} in the loop.  I don't have enough historical shell 
knowledge here to know if only certain shells promise support for this syntax.  
I suppose I could change this to call {{seq}}, which is part of coreutils, but 
then I don't really know the portability promises on that one either.

[~aw], can I get some advice from you?  What would be the most portable way to 
write the following kind of loop?

{code}
for i in {1..4}; do mkdir -p myDirectory/$i; done
{code}


> Enable parallel JUnit tests in pre-commit.
> ------------------------------------------
>
>                 Key: HADOOP-11984
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11984
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build, scripts, test
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: HADOOP-11984.001.patch, HADOOP-11984.002.patch, 
> HADOOP-11984.003.patch, HADOOP-11984.004.patch, HADOOP-11984.005.patch, 
> HADOOP-11984.006.patch, HADOOP-11984.007.patch, HADOOP-11984.008.patch, 
> HADOOP-11984.009.patch, HADOOP-11984.010.patch, HADOOP-11984.011.patch
>
>
> HADOOP-9287 and related issues implemented the parallel-tests Maven profile 
> for running JUnit tests in multiple concurrent processes.  This issue 
> proposes to activate that profile during pre-commit to speed up execution.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to