[Ci-users] gluster_glusterd2 builds failing by failing to set github status

Thu Aug 11 06:54:11 UTC 2016
Kaushal M <kshlmster at gmail.com>

On Thu, Aug 11, 2016 at 12:18 AM, Brian Stinson <brian at bstinson.com> wrote:
> On Aug 08 15:08, Kaushal M wrote:
>> On Wed, Aug 3, 2016 at 4:55 PM, Kaushal M <kshlmster at gmail.com> wrote:
>> > Hi all,
>> >
>> > So I've got centos-ci reporting status back to github for the
>> > gluster_glusterd2 job.
>> >
>> > But the builds still get marked as failures because Jenkins still
>> > apparantly fails to report back to Github. For eg., [1] is a build
>> > started for [2], which has been marked as a failure because reporting
>> > failed. But this failure was still reported back.
>> >
>> > In the console output, the actual build finishes at the end of `make
>> > test`. Which is a success.
>> >
>> > But I see two other 'Setting commit status' messages of which one
>> > failed, and caused the build to be marked as a failure.
>> >
>> > Has anyone seen this before, and know why it happens? And how can this be fixed?
>>
>> This also happens with the gluster_heketi-functional job.
>> Can anyone help us fix this?
>>
>> >
>> > ~kaushal
>> >
>> > [1]: https://ci.centos.org/job/gluster_glusterd2/7/console
>> > [2]: https://github.com/gluster/glusterd2/pull/117
>
> Looking at your job definitions, I noticed that you have this defined
> using 'Set status for Github Commit' Post-build actions. These shouldn't
> be needed if you're using the Github Pull Request Builder plugin (since
> GHPRB will set the status on the PR automatically for you).
>
> Hope this helps!

This fixed it. Thanks Brian.

~kaushal

>
> --Brian