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

Hadoop QA commented on MAPREDUCE-7023:
--------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} docker {color} | {color:red} 13m 
46s{color} | {color:red} Docker failed to build yetus/hadoop:5b98639. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | MAPREDUCE-7023 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12902061/MAPREDUCE-7023.001.patch
 |
| Console output | 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/7255/console |
| Powered by | Apache Yetus 0.7.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> TestHadoopArchiveLogs.testCheckFilesAndSeedApps fails on rerun
> --------------------------------------------------------------
>
>                 Key: MAPREDUCE-7023
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7023
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: test
>            Reporter: Gergely Novák
>            Assignee: Gergely Novák
>            Priority: Minor
>         Attachments: MAPREDUCE-7023.001.patch
>
>
> Since the test doesn't clean up the created "logs" dir, when rerunning it 
> fails on this line:
> {code}
> Assert.assertEquals(0, hal.eligibleApplications.size());
> hal.checkFilesAndSeedApps(fs, rootLogDir, suffix);
>  >>> Assert.assertEquals(1, hal.eligibleApplications.size());
> java.lang.AssertionError: 
> Expected :1
> Actual   :2 (or more for consecutive reruns)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to