hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roger Hoover <roger.hoo...@gmail.com>
Subject Re: Failed: YARN-412 PreCommit Build #638
Date Wed, 03 Apr 2013 17:26:28 GMT
Thank you, Hitesh.  This is exactly what I was looking for.


On Mon, Apr 1, 2013 at 5:55 PM, Hitesh Shah <hitesh@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.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message