You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2013/04/01 21:17:11 UTC

Failed: YARN-412 PreCommit Build #638

Jira: https://issues.apache.org/jira/browse/YARN-412
Build: https://builds.apache.org/job/PreCommit-YARN-Build/638/

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 67 lines...]


Going to apply patch with: /usr/bin/patch -p0
patching file hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/FifoScheduler.java
patching file hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/MockNodes.java
patching file hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/TestFifoScheduler.java


======================================================================
======================================================================
    Determining number of patched javac warnings.
======================================================================
======================================================================


/home/jenkins/tools/maven/latest/bin/mvn clean test -DskipTests -DHadoopPatchProcess -Pnative -Ptest-patch > /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/patchprocess/patchJavacWarnings.txt 2>&1




{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12576418/YARN-412.patch
  against trunk revision .

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

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

    {color:red}-1 javac{color:red}.  The patch appears to cause the build to fail.

Console output: https://builds.apache.org/job/PreCommit-YARN-Build/638//console

This message is automatically generated.


======================================================================
======================================================================
    Adding comment to Jira.
======================================================================
======================================================================


Comment added.
1fb0ab8762458fd274a548d0d8fa290a83db007d logged out


======================================================================
======================================================================
    Finished build.
======================================================================
======================================================================


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###################################################################################
############################## FAILED TESTS (if any) ##############################
No tests ran.

Success: YARN-516 PreCommit Build #642

Posted by Apache Jenkins Server <je...@builds.apache.org>.
Jira: https://issues.apache.org/jira/browse/YARN-516
Build: https://builds.apache.org/job/PreCommit-YARN-Build/642/

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 2749 lines...]

/bin/kill -9 24043 
kill: No such process
NOP




{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12576471/YARN-516.txt
  against trunk revision .

    {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}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

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

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

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager.

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

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

This message is automatically generated.


======================================================================
======================================================================
    Adding comment to Jira.
======================================================================
======================================================================


Comment added.
fac824f3011470a778f8f41a16c9d43d34e65a1a logged out


======================================================================
======================================================================
    Finished build.
======================================================================
======================================================================


Archiving artifacts
Description set: YARN-516
Recording test results
Email was triggered for: Success
Sending email for trigger: Success



###################################################################################
############################## FAILED TESTS (if any) ##############################
All tests passed

Failed: YARN-467 PreCommit Build #641

Posted by Apache Jenkins Server <je...@builds.apache.org>.
Jira: https://issues.apache.org/jira/browse/YARN-467
Build: https://builds.apache.org/job/PreCommit-YARN-Build/641/

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 2962 lines...]
NOP




{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12576466/yarn-467-20130401.patch
  against trunk revision .

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

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

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

    {color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 2 warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version 1.3.9) 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 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager:

                  org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

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

This message is automatically generated.


======================================================================
======================================================================
    Adding comment to Jira.
======================================================================
======================================================================


Comment added.
b7e2cf963d08b9e29c8b0cfdd15b823c70b786f5 logged out


======================================================================
======================================================================
    Finished build.
======================================================================
======================================================================


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###################################################################################
############################## FAILED TESTS (if any) ##############################
1 tests failed.
FAILED:  org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer.testContainerLocalizerMain

Error Message:
 Argument(s) are different! Wanted: localFs.mkdir(     file:/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer/0/usercache/yak/filecache,     isA(org.apache.hadoop.fs.permission.FsPermission),     false ); -> at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer.testContainerLocalizerMain(TestContainerLocalizer.java:139) Actual invocation has different arguments: localFs.mkdir(     /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer/0/usercache/yak/filecache,     rwxr-xr-x,     false ); -> at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer.testContainerLocalizerMain(TestContainerLocalizer.java:132) 

Stack Trace:
Argument(s) are different! Wanted:
localFs.mkdir(
    file:/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer/0/usercache/yak/filecache,
    isA(org.apache.hadoop.fs.permission.FsPermission),
    false
);
-> at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer.testContainerLocalizerMain(TestContainerLocalizer.java:139)
Actual invocation has different arguments:
localFs.mkdir(
    /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer/0/usercache/yak/filecache,
    rwxr-xr-x,
    false
);
-> at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer.testContainerLocalizerMain(TestContainerLocalizer.java:132)

	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
	at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer.testContainerLocalizerMain(TestContainerLocalizer.java:139)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
	at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)



Failed: YARN-309 PreCommit Build #640

Posted by Apache Jenkins Server <je...@builds.apache.org>.
Jira: https://issues.apache.org/jira/browse/YARN-309
Build: https://builds.apache.org/job/PreCommit-YARN-Build/640/

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 3206 lines...]
NOP




{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12576449/YARN-309.11.patch
  against trunk revision .

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

    {color:green}+1 tests included{color}.  The patch appears to include 3 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}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version 1.3.9) 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 hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:

                  org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

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

This message is automatically generated.


======================================================================
======================================================================
    Adding comment to Jira.
======================================================================
======================================================================


Comment added.
d1fdff82dcb03c481990e161d246203c968f4ff9 logged out


======================================================================
======================================================================
    Finished build.
======================================================================
======================================================================


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###################################################################################
############################## FAILED TESTS (if any) ##############################
1 tests failed.
FAILED:  org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer.testContainerLocalizerMain

Error Message:
 Argument(s) are different! Wanted: localFs.mkdir(     file:/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer/0/usercache/yak/filecache,     isA(org.apache.hadoop.fs.permission.FsPermission),     false ); -> at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer.testContainerLocalizerMain(TestContainerLocalizer.java:139) Actual invocation has different arguments: localFs.mkdir(     /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer/0/usercache/yak/filecache,     rwxr-xr-x,     false ); -> at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer.testContainerLocalizerMain(TestContainerLocalizer.java:132) 

Stack Trace:
Argument(s) are different! Wanted:
localFs.mkdir(
    file:/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer/0/usercache/yak/filecache,
    isA(org.apache.hadoop.fs.permission.FsPermission),
    false
);
-> at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer.testContainerLocalizerMain(TestContainerLocalizer.java:139)
Actual invocation has different arguments:
localFs.mkdir(
    /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer/0/usercache/yak/filecache,
    rwxr-xr-x,
    false
);
-> at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer.testContainerLocalizerMain(TestContainerLocalizer.java:132)

	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
	at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer.testContainerLocalizerMain(TestContainerLocalizer.java:139)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
	at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)



Failed: YARN-444 PreCommit Build #639

Posted by Apache Jenkins Server <je...@builds.apache.org>.
Jira: https://issues.apache.org/jira/browse/YARN-444
Build: https://builds.apache.org/job/PreCommit-YARN-Build/639/

###################################################################################
########################## LAST 60 LINES OF THE CONSOLE ###########################
[...truncated 3397 lines...]
NOP




{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12576433/YARN-444-1.patch
  against trunk revision .

    {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}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version 1.3.9) 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 hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager:

                  org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

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

This message is automatically generated.


======================================================================
======================================================================
    Adding comment to Jira.
======================================================================
======================================================================


Comment added.
09b82939eeece0c70dae1cfebdda1a47db2c7671 logged out


======================================================================
======================================================================
    Finished build.
======================================================================
======================================================================


Build step 'Execute shell' marked build as failure
Archiving artifacts
[description-setter] Could not determine description.
Recording test results
Email was triggered for: Failure
Sending email for trigger: Failure



###################################################################################
############################## FAILED TESTS (if any) ##############################
1 tests failed.
FAILED:  org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer.testContainerLocalizerMain

Error Message:
 Argument(s) are different! Wanted: localFs.mkdir(     file:/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer/0/usercache/yak/filecache,     isA(org.apache.hadoop.fs.permission.FsPermission),     false ); -> at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer.testContainerLocalizerMain(TestContainerLocalizer.java:139) Actual invocation has different arguments: localFs.mkdir(     /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer/0/usercache/yak/filecache,     rwxr-xr-x,     false ); -> at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer.testContainerLocalizerMain(TestContainerLocalizer.java:132) 

Stack Trace:
Argument(s) are different! Wanted:
localFs.mkdir(
    file:/home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer/0/usercache/yak/filecache,
    isA(org.apache.hadoop.fs.permission.FsPermission),
    false
);
-> at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer.testContainerLocalizerMain(TestContainerLocalizer.java:139)
Actual invocation has different arguments:
localFs.mkdir(
    /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/target/org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer/0/usercache/yak/filecache,
    rwxr-xr-x,
    false
);
-> at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer.testContainerLocalizerMain(TestContainerLocalizer.java:132)

	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
	at org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.TestContainerLocalizer.testContainerLocalizerMain(TestContainerLocalizer.java:139)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
	at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
	at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
	at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
	at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
	at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
	at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)



Re: Failed: YARN-412 PreCommit Build #638

Posted by Roger Hoover <ro...@gmail.com>.
Thank you, Hitesh.  This is exactly what I was looking for.


On Mon, Apr 1, 2013 at 5:55 PM, Hitesh Shah <hi...@hortonworks.com> wrote:

> Hello Roger,
>
> Please take a look at
> https://builds.apache.org/job/PreCommit-YARN-Build/638/artifact/trunk/patchprocess/patchJavacWarnings.txt
>
> It shows a compile time failure.  I have added details to the jira.
>
> -- Hitesh
>
> On Apr 1, 2013, at 1:07 PM, Roger Hoover wrote:
>
> > Hi,
> >
> > Any ideas what caused this build failure?  It seems like the mvn clean
> test
> > command failed but there are no error messages in the console log.
> >
> > Any help is appreciated.  Thanks,
> >
> > Roger
> >
> >
> > On Mon, Apr 1, 2013 at 12:17 PM, Apache Jenkins Server <
> > jenkins@builds.apache.org> wrote:
> >
> >> Jira: https://issues.apache.org/jira/browse/YARN-412
> >> Build: https://builds.apache.org/job/PreCommit-YARN-Build/638/
> >>
> >>
> >>
> ###################################################################################
> >> ########################## LAST 60 LINES OF THE CONSOLE
> >> ###########################
> >> [...truncated 67 lines...]
> >>
> >>
> >> Going to apply patch with: /usr/bin/patch -p0
> >> patching file
> >>
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/FifoScheduler.java
> >> patching file
> >>
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/MockNodes.java
> >> patching file
> >>
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/TestFifoScheduler.java
> >>
> >>
> >> ======================================================================
> >> ======================================================================
> >>    Determining number of patched javac warnings.
> >> ======================================================================
> >> ======================================================================
> >>
> >>
> >> /home/jenkins/tools/maven/latest/bin/mvn clean test -DskipTests
> >> -DHadoopPatchProcess -Pnative -Ptest-patch >
> >>
> /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/patchprocess/patchJavacWarnings.txt
> >> 2>&1
> >>
> >>
> >>
> >>
> >> {color:red}-1 overall{color}.  Here are the results of testing the
> latest
> >> attachment
> >>
> http://issues.apache.org/jira/secure/attachment/12576418/YARN-412.patch
> >>  against trunk revision .
> >>
> >>    {color:green}+1 @author{color}.  The patch does not contain any
> >> @author tags.
> >>
> >>    {color:green}+1 tests included{color}.  The patch appears to include
> 2
> >> new or modified test files.
> >>
> >>    {color:red}-1 javac{color:red}.  The patch appears to cause the build
> >> to fail.
> >>
> >> Console output:
> >> https://builds.apache.org/job/PreCommit-YARN-Build/638//console
> >>
> >> This message is automatically generated.
> >>
> >>
> >> ======================================================================
> >> ======================================================================
> >>    Adding comment to Jira.
> >> ======================================================================
> >> ======================================================================
> >>
> >>
> >> Comment added.
> >> 1fb0ab8762458fd274a548d0d8fa290a83db007d logged out
> >>
> >>
> >> ======================================================================
> >> ======================================================================
> >>    Finished build.
> >> ======================================================================
> >> ======================================================================
> >>
> >>
> >> Build step 'Execute shell' marked build as failure
> >> Archiving artifacts
> >> [description-setter] Could not determine description.
> >> Recording test results
> >> Email was triggered for: Failure
> >> Sending email for trigger: Failure
> >>
> >>
> >>
> >>
> >>
> ###################################################################################
> >> ############################## FAILED TESTS (if any)
> >> ##############################
> >> No tests ran.
>
>

Re: Failed: YARN-412 PreCommit Build #638

Posted by Hitesh Shah <hi...@hortonworks.com>.
Hello Roger, 

Please take a look at https://builds.apache.org/job/PreCommit-YARN-Build/638/artifact/trunk/patchprocess/patchJavacWarnings.txt 

It shows a compile time failure.  I have added details to the jira. 

-- Hitesh 

On Apr 1, 2013, at 1:07 PM, Roger Hoover wrote:

> Hi,
> 
> Any ideas what caused this build failure?  It seems like the mvn clean test
> command failed but there are no error messages in the console log.
> 
> Any help is appreciated.  Thanks,
> 
> Roger
> 
> 
> On Mon, Apr 1, 2013 at 12:17 PM, Apache Jenkins Server <
> jenkins@builds.apache.org> wrote:
> 
>> Jira: https://issues.apache.org/jira/browse/YARN-412
>> Build: https://builds.apache.org/job/PreCommit-YARN-Build/638/
>> 
>> 
>> ###################################################################################
>> ########################## LAST 60 LINES OF THE CONSOLE
>> ###########################
>> [...truncated 67 lines...]
>> 
>> 
>> Going to apply patch with: /usr/bin/patch -p0
>> patching file
>> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/FifoScheduler.java
>> patching file
>> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/MockNodes.java
>> patching file
>> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/TestFifoScheduler.java
>> 
>> 
>> ======================================================================
>> ======================================================================
>>    Determining number of patched javac warnings.
>> ======================================================================
>> ======================================================================
>> 
>> 
>> /home/jenkins/tools/maven/latest/bin/mvn clean test -DskipTests
>> -DHadoopPatchProcess -Pnative -Ptest-patch >
>> /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/patchprocess/patchJavacWarnings.txt
>> 2>&1
>> 
>> 
>> 
>> 
>> {color:red}-1 overall{color}.  Here are the results of testing the latest
>> attachment
>>  http://issues.apache.org/jira/secure/attachment/12576418/YARN-412.patch
>>  against trunk revision .
>> 
>>    {color:green}+1 @author{color}.  The patch does not contain any
>> @author tags.
>> 
>>    {color:green}+1 tests included{color}.  The patch appears to include 2
>> new or modified test files.
>> 
>>    {color:red}-1 javac{color:red}.  The patch appears to cause the build
>> to fail.
>> 
>> Console output:
>> https://builds.apache.org/job/PreCommit-YARN-Build/638//console
>> 
>> This message is automatically generated.
>> 
>> 
>> ======================================================================
>> ======================================================================
>>    Adding comment to Jira.
>> ======================================================================
>> ======================================================================
>> 
>> 
>> Comment added.
>> 1fb0ab8762458fd274a548d0d8fa290a83db007d logged out
>> 
>> 
>> ======================================================================
>> ======================================================================
>>    Finished build.
>> ======================================================================
>> ======================================================================
>> 
>> 
>> Build step 'Execute shell' marked build as failure
>> Archiving artifacts
>> [description-setter] Could not determine description.
>> Recording test results
>> Email was triggered for: Failure
>> Sending email for trigger: Failure
>> 
>> 
>> 
>> 
>> ###################################################################################
>> ############################## FAILED TESTS (if any)
>> ##############################
>> No tests ran.


Re: Failed: YARN-412 PreCommit Build #638

Posted by Roger Hoover <ro...@gmail.com>.
Hi,

Any ideas what caused this build failure?  It seems like the mvn clean test
command failed but there are no error messages in the console log.

Any help is appreciated.  Thanks,

Roger


On Mon, Apr 1, 2013 at 12:17 PM, Apache Jenkins Server <
jenkins@builds.apache.org> wrote:

> Jira: https://issues.apache.org/jira/browse/YARN-412
> Build: https://builds.apache.org/job/PreCommit-YARN-Build/638/
>
>
> ###################################################################################
> ########################## LAST 60 LINES OF THE CONSOLE
> ###########################
> [...truncated 67 lines...]
>
>
> Going to apply patch with: /usr/bin/patch -p0
> patching file
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/FifoScheduler.java
> patching file
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/MockNodes.java
> patching file
> hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fifo/TestFifoScheduler.java
>
>
> ======================================================================
> ======================================================================
>     Determining number of patched javac warnings.
> ======================================================================
> ======================================================================
>
>
> /home/jenkins/tools/maven/latest/bin/mvn clean test -DskipTests
> -DHadoopPatchProcess -Pnative -Ptest-patch >
> /home/jenkins/jenkins-slave/workspace/PreCommit-YARN-Build/patchprocess/patchJavacWarnings.txt
> 2>&1
>
>
>
>
> {color:red}-1 overall{color}.  Here are the results of testing the latest
> attachment
>   http://issues.apache.org/jira/secure/attachment/12576418/YARN-412.patch
>   against trunk revision .
>
>     {color:green}+1 @author{color}.  The patch does not contain any
> @author tags.
>
>     {color:green}+1 tests included{color}.  The patch appears to include 2
> new or modified test files.
>
>     {color:red}-1 javac{color:red}.  The patch appears to cause the build
> to fail.
>
> Console output:
> https://builds.apache.org/job/PreCommit-YARN-Build/638//console
>
> This message is automatically generated.
>
>
> ======================================================================
> ======================================================================
>     Adding comment to Jira.
> ======================================================================
> ======================================================================
>
>
> Comment added.
> 1fb0ab8762458fd274a548d0d8fa290a83db007d logged out
>
>
> ======================================================================
> ======================================================================
>     Finished build.
> ======================================================================
> ======================================================================
>
>
> Build step 'Execute shell' marked build as failure
> Archiving artifacts
> [description-setter] Could not determine description.
> Recording test results
> Email was triggered for: Failure
> Sending email for trigger: Failure
>
>
>
>
> ###################################################################################
> ############################## FAILED TESTS (if any)
> ##############################
> No tests ran.