On 03/04/2020 11.20, Ryan Schmidt wrote:
> True, but 10.15 is missing because we have failed to produce a 10.15 version
> of MacPorts base for it to use. Short term, we should do that. Long term, we
> should fix it so that the CI systems can use the standard version of MacPorts
> base and don't
Considering that XCode 11.4 will only run on 10.15, we should probably do
that as soon as possible. We also might want to ditch travis. I barely pay
attention to it anymore. Does anyone else?
We also might want to consider github actions, which run on azure and can
link to what we do on Github
> On Apr 3, 2020, at 04:18, Christopher Jones wrote:
>
>
>> 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
> 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
On Apr 3, 2020, at 03:35, Xim wrote:
> Dear developers,
>
> About an hour ago I submitted a modified commit which only contains a typo
> fix in the note.
>
> To my surprise, Travis Build failed for two times, both reported that one of
> my dependencies failed.
> I checked the two logs.
>
Dear developers,
About an hour ago I submitted a modified commit which only contains a typo fix
in the note.
To my surprise, Travis Build failed for two times, both reported that one of my
dependencies failed.
I checked the two logs.
