syphilis has asked for the wisdom of the Perl Monks concerning the following question:

Hi,

At this pull request, Travis reports a failure.
So I go to the Travis build log where I can see the failing job (perl-5.14-thr).

Karen Etheridge once told me that in such a scenario I should be able to re-run the job, and this page that I googled agrees.
In fact, that page that I googled is very similar to the Travis build log that I linked to above.
The only siginificant differences I can see are that the build log I'm looking at contains neither the "Restart build" button, nor the various "Restart job" buttons down the RHS of the page.

Is it possible for me to re-run that particular failing job ?
AFAICT it's only failing because Travis can't find the perl-5.14 distro.

I know I can initiate a full rebuild by pushing some pointless inconsequential change (eg change in whitespace) to my forked repo.
Is that the only way ?

Should I just ignore that fail report and do nothing at all about it ? (Is such non-action deemed reasonable ? ... I'm not sure what the conventions are wrt this.)

Cheers,
Rob
  • Comment on [OT] Restarting Travis from a pull request

Replies are listed 'Best First'.
Re: [OT] Restarting Travis from a pull request
by choroba (Cardinal) on Feb 07, 2020 at 09:08 UTC
    You have to be a maintainer of the project in order to be allowed to restart a Travis build.

    Try closing and re-opening the pull request. It works here at work, but I'm not sure it's a general GitHub-Travis behaviour or a proprietary enhancement.

    map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
      You have to be a maintainer of the project in order to be allowed to restart a Travis build

      Ok - that would explain it.

      Try closing and re-opening the pull request

      Heh ... obviously you have a deep understanding of the basic principles of IT ;-)))
      Thankfully, the PR in question has since been merged (and closed) ... and I aint messin wif nuffin. (One doesn't poke at Islam, and one doesn't poke at Github.)

      Seriously - thanks for your response, choroba.
      And thanks also to marto, for making me aware of the lower level possibilities.

      Cheers,
      Rob
Re: [OT] Restarting Travis from a pull request
by marto (Cardinal) on Feb 07, 2020 at 09:50 UTC
      It failed with a probable GitHub hiccup:
      fatal: unable to connect to github.com: github.com[0: 192.30.253.113]: errno=Connection timed out
      map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]

        Thanks, missed that. Some searching shows this not to be isolated, with the suggestion of switching to https rather than git://, to avoid timeouts (apparently), weird proxy configs etc.