A currently unstable CI?

Christopher Jones jonesc at hep.phy.cam.ac.uk
Fri Apr 3 09:18:14 UTC 2020

> No action necessary. Both builds failed because "Could not resolve host". Unfortunately we see these types of network errors rather frequently from Travis CI and we do not know how to get the Travis people to resolve it. It does not appear to be a very good service. We also use the Azure Pipelines service which as far as I know has not had these problems. Maybe we should stop using the Travis CI service altogether.

Azure is more stable, but is currently limited in that it only seems to support 10.14 builds. 10.13 was recently removed, and support for 10.15 is missing. So if where where to use only azure we would be quite limited in terms of OS testing.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20200403/dc86210b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1930 bytes
Desc: not available
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20200403/dc86210b/attachment.bin>

More information about the macports-dev mailing list