restarting failed PR builds

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

restarting failed PR builds

Ben Coman
 
Hi Nicolas,

Thanks for looking at Gerardo's snprintf PR.
Now I think its build failures were due to something else happening a
month ago (as you commented), but the snprintf PR doesn't get rebuilt
after those were fixed.
Several other PRs seem in the same boat - but then I think the red
cross discourages people from reviewing them.

I read [1] that one way to retrigger a build is to close and re-open
the PR.  Maybe you could test that? Ideally there would be green ticks
before merging, rather than ignoring the red crosses since we "know"
they are unrelated.  I'd do it but I think repo write permission is
needed.

cheers -ben




[1]  http://stackoverflow.com/questions/17606874/trigger-a-travis-ci-rebuild-without-pushing-a-commit
Reply | Threaded
Open this post in threaded view
|

Re: restarting failed PR builds

fniephaus
 

On Mon, Nov 14, 2016 at 3:05 PM Ben Coman <[hidden email]> wrote:

Hi Nicolas,

Thanks for looking at Gerardo's snprintf PR.
Now I think its build failures were due to something else happening a
month ago (as you commented), but the snprintf PR doesn't get rebuilt
after those were fixed.
Several other PRs seem in the same boat - but then I think the red
cross discourages people from reviewing them.

I read [1] that one way to retrigger a build is to close and re-open
the PR.  Maybe you could test that? Ideally there would be green ticks
before merging, rather than ignoring the red crosses since we "know"
they are unrelated.  I'd do it but I think repo write permission is
needed.

You could also just merge the Cog branch into the PR branch.
This should trigger a new build as well.

Cheers,
Fabio
 

cheers -ben




[1]  http://stackoverflow.com/questions/17606874/trigger-a-travis-ci-rebuild-without-pushing-a-commit