Re: continuing releases on Apache Hadoop 2.6.x

2015-11-20 Thread Junping Du 
+1. Early Dec sounds too early for 2.6.3 release given we only have 18 patches 
since recently release 2.6.2.
We should nominate more fixes and wait a while for the feedback on 2.6.2.

Thanks,

Junping

From: Vinod Vavilapalli 
Sent: Thursday, November 19, 2015 11:34 PM
To: yarn-...@hadoop.apache.org
Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org
Subject: Re: continuing releases on Apache Hadoop 2.6.x

I see 18 JIRAs across the sub-projects as of now in 2.6.3. Seems like we will 
have a reasonable number of fixes if we start an RC early december.

In the mean while, we should also review 2.7.3 and 2.8.0 blocker / critical 
list and see if it makes sense to backport any of those into 2.6.3.

+Vinod


On Nov 17, 2015, at 5:10 PM, Sangjin Lee 
> wrote:

I'd like to pick up this email discussion again. It is time that we started
thinking about the next release in the 2.6.x line. IMO we want to walk the
balance between maintaining a reasonable release cadence and getting a good
amount of high-quality fixes. The timeframe is a little tricky as the
holidays are approaching. If we have enough fixes accumulated in
branch-2.6, some time early December might be a good target for cutting the
first release candidate. Once we miss that window, I think we are looking
at next January. I'd like to hear your thoughts on this.

Re: continuing releases on Apache Hadoop 2.6.x

2015-11-20 Thread Sean Busbey 
Early december would be great, presuming the RC process doesn't take too
long. By then it'll already have over a month since the 2.6.2 release and
I'm sure the folks contributing the 18 patches we already have in would
like to see their work out there.

On Fri, Nov 20, 2015 at 7:51 AM, Junping Du  wrote:

> +1. Early Dec sounds too early for 2.6.3 release given we only have 18
> patches since recently release 2.6.2.
> We should nominate more fixes and wait a while for the feedback on 2.6.2.
>
> Thanks,
>
> Junping
> 
> From: Vinod Vavilapalli 
> Sent: Thursday, November 19, 2015 11:34 PM
> To: yarn-...@hadoop.apache.org
> Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org;
> mapreduce-...@hadoop.apache.org
> Subject: Re: continuing releases on Apache Hadoop 2.6.x
>
> I see 18 JIRAs across the sub-projects as of now in 2.6.3. Seems like we
> will have a reasonable number of fixes if we start an RC early december.
>
> In the mean while, we should also review 2.7.3 and 2.8.0 blocker /
> critical list and see if it makes sense to backport any of those into 2.6.3.
>
> +Vinod
>
>
> On Nov 17, 2015, at 5:10 PM, Sangjin Lee > wrote:
>
> I'd like to pick up this email discussion again. It is time that we started
> thinking about the next release in the 2.6.x line. IMO we want to walk the
> balance between maintaining a reasonable release cadence and getting a good
> amount of high-quality fixes. The timeframe is a little tricky as the
> holidays are approaching. If we have enough fixes accumulated in
> branch-2.6, some time early December might be a good target for cutting the
> first release candidate. Once we miss that window, I think we are looking
> at next January. I'd like to hear your thoughts on this.
>
>


-- 
Sean

Re: continuing releases on Apache Hadoop 2.6.x

2015-11-20 Thread Sangjin Lee 
It would be great if we can get enough number of fixes by early December.
18 seems bit on the low side, but if we lose this window it won't be until
next year.

As for the release management, thanks Chris, Junping, and Haohui for
volunteering! I'll reach out to you to discuss what we do with 2.6.3. I
assume we will have more maintenance releases in the 2.6.x line, so there
will be more opportunities. We do need one person with PMC privileges to be
able to go through all the release management steps without assistance,
which I learned last time.

Regards,
Sangjin

On Fri, Nov 20, 2015 at 10:03 AM, Sean Busbey  wrote:

> Early december would be great, presuming the RC process doesn't take too
> long. By then it'll already have over a month since the 2.6.2 release and
> I'm sure the folks contributing the 18 patches we already have in would
> like to see their work out there.
>
> On Fri, Nov 20, 2015 at 7:51 AM, Junping Du  wrote:
>
> > +1. Early Dec sounds too early for 2.6.3 release given we only have 18
> > patches since recently release 2.6.2.
> > We should nominate more fixes and wait a while for the feedback on 2.6.2.
> >
> > Thanks,
> >
> > Junping
> > 
> > From: Vinod Vavilapalli 
> > Sent: Thursday, November 19, 2015 11:34 PM
> > To: yarn-...@hadoop.apache.org
> > Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org;
> > mapreduce-...@hadoop.apache.org
> > Subject: Re: continuing releases on Apache Hadoop 2.6.x
> >
> > I see 18 JIRAs across the sub-projects as of now in 2.6.3. Seems like we
> > will have a reasonable number of fixes if we start an RC early december.
> >
> > In the mean while, we should also review 2.7.3 and 2.8.0 blocker /
> > critical list and see if it makes sense to backport any of those into
> 2.6.3.
> >
> > +Vinod
> >
> >
> > On Nov 17, 2015, at 5:10 PM, Sangjin Lee  sj...@apache.org>> wrote:
> >
> > I'd like to pick up this email discussion again. It is time that we
> started
> > thinking about the next release in the 2.6.x line. IMO we want to walk
> the
> > balance between maintaining a reasonable release cadence and getting a
> good
> > amount of high-quality fixes. The timeframe is a little tricky as the
> > holidays are approaching. If we have enough fixes accumulated in
> > branch-2.6, some time early December might be a good target for cutting
> the
> > first release candidate. Once we miss that window, I think we are looking
> > at next January. I'd like to hear your thoughts on this.
> >
> >
>
>
> --
> Sean
>

FYI: now using dev-support/docker/Dockerfile

2015-11-20 Thread Allen Wittenauer 

I’ve switched the Jenkins builds over to use the Hadoop-bundled 
Dockerfile.  This means that external dependencies are now controlled by 
Hadoop-itself.  If a patch is submitted to a branch that doesn’t have that 
file, it should rollback to the default Yetus one.

Build failed in Jenkins: Hadoop-Common-trunk #2011

2015-11-20 Thread Apache Jenkins Server 
See 

Changes:

[jlowe] YARN-4374. RM capacity scheduler UI rounds user limit factor.

--
[...truncated 5876 lines...]
Running org.apache.hadoop.fs.contract.localfs.TestLocalFSContractCreate
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.028 sec - in 
org.apache.hadoop.fs.contract.localfs.TestLocalFSContractCreate
Running org.apache.hadoop.fs.contract.localfs.TestLocalFSContractSetTimes
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.42 sec - in 
org.apache.hadoop.fs.contract.localfs.TestLocalFSContractSetTimes
Running org.apache.hadoop.fs.contract.localfs.TestLocalFSContractSeek
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.593 sec - in 
org.apache.hadoop.fs.contract.localfs.TestLocalFSContractSeek
Running org.apache.hadoop.fs.TestContentSummary
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.813 sec - in 
org.apache.hadoop.fs.TestContentSummary
Running org.apache.hadoop.fs.TestTrash
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 22.515 sec - in 
org.apache.hadoop.fs.TestTrash
Running org.apache.hadoop.fs.TestLocalFSFileContextCreateMkdir
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.154 sec - in 
org.apache.hadoop.fs.TestLocalFSFileContextCreateMkdir
Running org.apache.hadoop.fs.TestLocalFsFCStatistics
Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 11.905 sec <<< 
FAILURE! - in org.apache.hadoop.fs.TestLocalFsFCStatistics
testStatisticsThreadLocalDataCleanUp(org.apache.hadoop.fs.TestLocalFsFCStatistics)
  Time elapsed: 10.277 sec  <<< ERROR!
java.util.concurrent.TimeoutException: Timed out waiting for condition. Thread 
diagnostics:
Timestamp: 2015-11-21 12:12:13,841

"Thread-6"  prio=5 tid=15 runnable
java.lang.Thread.State: RUNNABLE
at java.lang.Thread.dumpThreads(Native Method)
at java.lang.Thread.getAllStackTraces(Thread.java:1640)
at 
org.apache.hadoop.test.TimedOutTestsListener.buildThreadDump(TimedOutTestsListener.java:87)
at 
org.apache.hadoop.test.TimedOutTestsListener.buildThreadDiagnosticString(TimedOutTestsListener.java:73)
at 
org.apache.hadoop.test.GenericTestUtils.waitFor(GenericTestUtils.java:186)
at 
org.apache.hadoop.fs.FCStatisticsBaseTest.testStatisticsThreadLocalDataCleanUp(FCStatisticsBaseTest.java:143)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)
"process reaper" daemon prio=10 tid=9 timed_waiting
java.lang.Thread.State: TIMED_WAITING
at sun.misc.Unsafe.park(Native Method)
at 
java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
at 
java.util.concurrent.SynchronousQueue$TransferStack.awaitFulfill(SynchronousQueue.java:460)
at 
java.util.concurrent.SynchronousQueue$TransferStack.transfer(SynchronousQueue.java:359)
at java.util.concurrent.SynchronousQueue.poll(SynchronousQueue.java:942)
at 
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
"org.apache.hadoop.fs.FileSystem$Statistics$StatisticsDataReferenceCleaner" 
daemon prio=5 tid=12 in Object.wait()
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
at 
org.apache.hadoop.fs.FileSystem$Statistics$StatisticsDataReferenceCleaner.run(FileSystem.java:3109)
at java.lang.Thread.run(Thread.java:745)
"main"  prio=5 tid=1 timed_waiting
java.lang.Thread.State: TIMED_WAITING
at java.lang.Object.wait(Native Method)
at java.lang.Thread.join(Thread.java:1289)
at 
org.junit.internal.runners.statements.FailOnTimeout.evaluateStatement(FailOnTimeout.java:26)
at 
org.junit.internal.runners.statements.FailOnTimeout.evaluate(FailOnTimeout.java:17)
at

Build failed in Jenkins: Hadoop-common-trunk-Java8 #717

2015-11-20 Thread Apache Jenkins Server 
See 

Changes:

[jlowe] YARN-4374. RM capacity scheduler UI rounds user limit factor.

[wangda] YARN-3769. Consider user limit when calculating total pending resource

--
[...truncated 5862 lines...]
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.461 sec - in 
org.apache.hadoop.util.hash.TestHash
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.util.TestPureJavaCrc32
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.787 sec - in 
org.apache.hadoop.util.TestPureJavaCrc32
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.util.TestNativeLibraryChecker
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.513 sec - in 
org.apache.hadoop.util.TestNativeLibraryChecker
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.util.TestProtoUtil
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.328 sec - in 
org.apache.hadoop.util.TestProtoUtil
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.util.TestStringUtils
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.388 sec - in 
org.apache.hadoop.util.TestStringUtils
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.util.TestSignalLogger
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.194 sec - in 
org.apache.hadoop.util.TestSignalLogger
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.util.TestStringInterner
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.126 sec - in 
org.apache.hadoop.util.TestStringInterner
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.util.TestRunJar
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.441 sec - in 
org.apache.hadoop.util.TestRunJar
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.util.TestProgress
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.22 sec - in 
org.apache.hadoop.util.TestProgress
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.util.TestReflectionUtils
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.576 sec - in 
org.apache.hadoop.util.TestReflectionUtils
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.util.TestVersionUtil
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.219 sec - in 
org.apache.hadoop.util.TestVersionUtil
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.util.TestWinUtils
Tests run: 11, Failures: 0, Errors: 0, Skipped: 11, Time elapsed: 0.238 sec - 
in org.apache.hadoop.util.TestWinUtils
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.util.TestIndexedSort
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.963 sec - in 
org.apache.hadoop.util.TestIndexedSort
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.util.TestGSet
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.264 sec - in 
org.apache.hadoop.util.TestGSet
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.util.TestHttpExceptionUtils
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.814 sec - in 
org.apache.hadoop.util.TestHttpExceptionUtils
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.util.TestAsyncDiskService
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.225 sec - in 
org.apache.hadoop.util.TestAsyncDiskService
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.util.TestNodeHealthScriptRunner
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.853 sec - in 
org.apache.hadoop.util.TestNodeHealthScriptRunner
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.util.bloom.TestBloomFilters
Tests run: 6, Failures: 0,

Jenkins build is back to normal : Hadoop-Common-trunk #2012

2015-11-20 Thread Apache Jenkins Server 
See

Build failed in Jenkins: Hadoop-common-trunk-Java8 #718

2015-11-20 Thread Apache Jenkins Server 
See 

Changes:

[wangda] move YARN-4326/YARN-3849 from 2.8.0 to 2.7.3

--
[...truncated 6245 lines...]
at 
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1066)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1127)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:744)
"main"  prio=5 tid=1 timed_waiting
java.lang.Thread.State: TIMED_WAITING
at java.lang.Object.wait(Native Method)
at java.lang.Thread.join(Thread.java:1252)
at 
org.junit.internal.runners.statements.FailOnTimeout.evaluateStatement(FailOnTimeout.java:26)
at 
org.junit.internal.runners.statements.FailOnTimeout.evaluate(FailOnTimeout.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)


at 
org.apache.hadoop.test.GenericTestUtils.waitFor(GenericTestUtils.java:188)
at 
org.apache.hadoop.fs.FCStatisticsBaseTest.testStatisticsThreadLocalDataCleanUp(FCStatisticsBaseTest.java:143)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74)

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.fs.TestFileStatus
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.528 sec - in 
org.apache.hadoop.fs.TestFileStatus
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.fs.TestCommandFormat
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.209 sec - in 
org.apache.hadoop.fs.TestCommandFormat
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.jmx.TestJMXJsonServlet
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.649 sec - in 
org.apache.hadoop.jmx.TestJMXJsonServlet
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.http.TestGlobalFilter
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.608 sec - in 
org.apache.hadoop.http.TestGlobalFilter
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.http.TestPathFilter
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.571 sec - in 
org.apache.hadoop.http.TestPathFilter
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=768m; 
support was removed in 8.0
Running org.apache.hadoop.http.TestHttpCookieFlag
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.057 sec - in

Build failed in Jenkins: Hadoop-Common-trunk #2013

2015-11-20 Thread Apache Jenkins Server 
See 

Changes:

[wangda] move YARN-4326/YARN-3849 from 2.8.0 to 2.7.3

--
[...truncated 5621 lines...]
Running org.apache.hadoop.fs.TestBlockLocation
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.26 sec - in 
org.apache.hadoop.fs.TestBlockLocation
Running org.apache.hadoop.fs.TestFsShellCopy
Tests run: 16, Failures: 0, Errors: 0, Skipped: 4, Time elapsed: 2.512 sec - in 
org.apache.hadoop.fs.TestFsShellCopy
Running org.apache.hadoop.fs.permission.TestAcl
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.364 sec - in 
org.apache.hadoop.fs.permission.TestAcl
Running org.apache.hadoop.fs.permission.TestFsPermission
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.196 sec - in 
org.apache.hadoop.fs.permission.TestFsPermission
Running org.apache.hadoop.fs.sftp.TestSFTPFileSystem
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 12.701 sec - in 
org.apache.hadoop.fs.sftp.TestSFTPFileSystem
Running org.apache.hadoop.fs.TestFileContextDeleteOnExit
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.521 sec - in 
org.apache.hadoop.fs.TestFileContextDeleteOnExit
Running org.apache.hadoop.fs.TestFcLocalFsUtil
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.543 sec - in 
org.apache.hadoop.fs.TestFcLocalFsUtil
Running org.apache.hadoop.fs.TestStat
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.416 sec - in 
org.apache.hadoop.fs.TestStat
Running org.apache.hadoop.fs.shell.TestCopy
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.958 sec - in 
org.apache.hadoop.fs.shell.TestCopy
Running org.apache.hadoop.fs.shell.TestTextCommand
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.114 sec - in 
org.apache.hadoop.fs.shell.TestTextCommand
Running org.apache.hadoop.fs.shell.TestCopyPreserveFlag
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.653 sec - in 
org.apache.hadoop.fs.shell.TestCopyPreserveFlag
Running org.apache.hadoop.fs.shell.TestAclCommands
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.799 sec - in 
org.apache.hadoop.fs.shell.TestAclCommands
Running org.apache.hadoop.fs.shell.find.TestFind
Tests run: 24, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 3.636 sec <<< 
FAILURE! - in org.apache.hadoop.fs.shell.find.TestFind
processArguments(org.apache.hadoop.fs.shell.find.TestFind)  Time elapsed: 1.997 
sec  <<< ERROR!
java.lang.Exception: test timed out after 1000 milliseconds
at java.util.AbstractList.(AbstractList.java:601)
at 
java.util.AbstractSequentialList.(AbstractSequentialList.java:74)
at java.util.LinkedList.(LinkedList.java:104)
at org.mockito.internal.util.ListUtil.filter(ListUtil.java:13)
at 
org.mockito.internal.invocation.InvocationsFinder.findAllMatchingUnverifiedChunks(InvocationsFinder.java:23)
at 
org.mockito.internal.verification.checkers.MissingInvocationInOrderChecker.check(MissingInvocationInOrderChecker.java:33)
at org.mockito.internal.verification.Times.verifyInOrder(Times.java:47)
at 
org.mockito.internal.verification.InOrderWrapper.verify(InOrderWrapper.java:30)
at 
org.mockito.internal.verification.MockAwareVerificationMode.verify(MockAwareVerificationMode.java:21)
at org.mockito.internal.MockHandler.handle(MockHandler.java:80)
at 
org.mockito.internal.creation.MethodInterceptorFilter.intercept(MethodInterceptorFilter.java:47)
at 
org.apache.hadoop.fs.shell.find.TestFind$FileStatusChecker$$EnhancerByMockitoWithCGLIB$$62dfc721.check()
at 
org.apache.hadoop.fs.shell.find.TestFind.processArguments(TestFind.java:278)

Running org.apache.hadoop.fs.shell.find.TestPrint0
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.84 sec - in 
org.apache.hadoop.fs.shell.find.TestPrint0
Running org.apache.hadoop.fs.shell.find.TestPrint
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.752 sec - in 
org.apache.hadoop.fs.shell.find.TestPrint
Running org.apache.hadoop.fs.shell.find.TestAnd
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.637 sec - in 
org.apache.hadoop.fs.shell.find.TestAnd
Running org.apache.hadoop.fs.shell.find.TestResult
Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.156 sec - in 
org.apache.hadoop.fs.shell.find.TestResult
Running org.apache.hadoop.fs.shell.find.TestIname
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.255 sec - in 
org.apache.hadoop.fs.shell.find.TestIname
Running org.apache.hadoop.fs.shell.find.TestName
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.93 sec - in 
org.apache.hadoop.fs.shell.find.TestName
Running org.apache.hadoop.fs.shell.find.TestFilterExpression
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.662 sec - in