[python-committers] How to force Travis to re-run?

[Alex Gaynor]

If you look at the travis-ui, do you see little "restart" arrows (example
attached)? Those are what do it -- I went ahead and restarted the failed
job on this one.

Alex

On Sat, Jan 6, 2018 at 11:43 AM, Eric V. Smith <eric at trueblade.com> wrote:

> I'm trying to merge this: https://github.com/python/cpython/pull/5113
>
> Travis failed, but not due to something in this PR (looks like a random
> networking failure). How do I trigger the Travis check to re-run? Or I
> guess just skipping it would be okay as a last resort, but I'd really like
> to try re-running it first.
>
> Thanks.
> Eric.
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>



-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
GPG Key fingerprint: D1B3 ADC0 E023 8CA6
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20180106/ffd997ed/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2018-01-06 at 11.45.20 AM.png
Type: image/png
Size: 7298 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-committers/attachments/20180106/ffd997ed/attachment.png>