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

Allen Wittenauer commented on YARN-4478:
----------------------------------------

Just an FYI, but there are two key problems that folks should be aware of:

#1:

None of the current hadoop jenkins "build project" jobs actually report all of 
the unit test failures in a consistent manner due to how maven works.  If a 
dependent module fails, then the parent module is never run.  In words:

Given two modules A, B.  Relationship is such that B requires A.  

If A's unit tests succeed, then B's unit tests are executed.

If A's unit tests fail, then B's unit tests are *never run*.

#2

I've already determined that a large chunk of the YARN unit tests CANNOT be run 
simultaneously due to TCP port usage.  (See YARN-4950).  This means that if two 
YARN nightlies are running on the same box at the same time, it's pretty much a 
100% certainty that there will be spurious failures. (Yetus guarantees 
some\-\-but not total\-\-isolation via docker, so precommit should be immune to 
this particular problem.)

That said, I've been working on a Yetus-based replacement for full compiles 
(YETUS-156).  This would at least solve major parts of both these issues. I've 
been running it in test for Hadoop for a while now:  
(https://builds.apache.org/view/H-L/view/Hadoop/job/hadoop-qbt-test ).  I've 
had unit tests turned off, but I just kicked off another run with the unit 
tests turned on so that you can see what happens.  

> [Umbrella] : Track all the Test failures in YARN
> ------------------------------------------------
>
>                 Key: YARN-4478
>                 URL: https://issues.apache.org/jira/browse/YARN-4478
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>            Reporter: Rohith Sharma K S
>
> Recently many test cases are failing either timed out or new bug fix caused 
> impact. Many test faiures JIRA are raised and are in progress.
> This is to track all the test failures JIRA's



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

Reply via email to