You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by Greg Hill <gr...@RACKSPACE.COM> on 2016/01/18 14:51:17 UTC

How to find build failures?

I have a patch up that it says fails the build, but I can't see any errors in the output. I was able to run mvn test locally fine, so it might just be an environmental difference I need to sort out.  It seems to log the actual maven output to a local file: /home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/patch-work/patchJavacWarnings.txt but that file would be overwritten by every patch test afaict. Maybe we should put that in the build folder instead so we can review it after the fact? Or just output to console so it gets logged in the job?

https://builds.apache.org/job/Ambari-trunk-test-patch/4948//console

Thanks in advance for any help/suggestions.

Greg

Re: How to find build failures?

Posted by Greg Hill <gr...@RACKSPACE.COM>.

Thanks, that's what I was looking for.

Greg

On 1/18/16, 10:45 AM, "Mithun Mathew" <mi...@gmail.com> wrote:

>Hi Greg
>
>Here's the artifact file with the error that might have caused the
>failure:
>https://builds.apache.org/job/Ambari-trunk-test-patch/4948/artifact/patch-
>work/patchJavacWarnings.txt
>
>Looks like ambari-shell/ambari-python-shell/pom.xml was deleted in the
>patch.
>
>Regards
>Matt
>
>On Mon, Jan 18, 2016 at 5:51 AM, Greg Hill <gr...@rackspace.com>
>wrote:
>
>> I have a patch up that it says fails the build, but I can't see any
>>errors
>> in the output. I was able to run mvn test locally fine, so it might
>>just be
>> an environmental difference I need to sort out.  It seems to log the
>>actual
>> maven output to a local file:
>> 
>>/home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/patch-work/
>>patchJavacWarnings.txt
>> but that file would be overwritten by every patch test afaict. Maybe we
>> should put that in the build folder instead so we can review it after
>>the
>> fact? Or just output to console so it gets logged in the job?
>>
>> https://builds.apache.org/job/Ambari-trunk-test-patch/4948//console
>>
>> Thanks in advance for any help/suggestions.
>>
>> Greg
>>
>
>
>
>-- 
>*Mithun Mathew* (Matt)
>
>   - www.linkedin.com/in/mithunmatt/

Re: How to find build failures?

Posted by Mithun Mathew <mi...@gmail.com>.

Hi Greg

Here's the artifact file with the error that might have caused the failure:
https://builds.apache.org/job/Ambari-trunk-test-patch/4948/artifact/patch-work/patchJavacWarnings.txt

Looks like ambari-shell/ambari-python-shell/pom.xml was deleted in the
patch.

Regards
Matt

On Mon, Jan 18, 2016 at 5:51 AM, Greg Hill <gr...@rackspace.com> wrote:

> I have a patch up that it says fails the build, but I can't see any errors
> in the output. I was able to run mvn test locally fine, so it might just be
> an environmental difference I need to sort out.  It seems to log the actual
> maven output to a local file:
> /home/jenkins/jenkins-slave/workspace/Ambari-trunk-test-patch/patch-work/patchJavacWarnings.txt
> but that file would be overwritten by every patch test afaict. Maybe we
> should put that in the build folder instead so we can review it after the
> fact? Or just output to console so it gets logged in the job?
>
> https://builds.apache.org/job/Ambari-trunk-test-patch/4948//console
>
> Thanks in advance for any help/suggestions.
>
> Greg
>



-- 
*Mithun Mathew* (Matt)

   - www.linkedin.com/in/mithunmatt/