On 2018-03-26 00:34, Mojca Miklavec wrote:
> On 26 March 2018 at 00:14, Rainer Müller wrote:
>> On 2018-03-25 06:11, Ryan Schmidt wrote:
>>>
>>> Currently PRs are tested by a separate build infrastructure on Travis. It
>>> runs on three systems: Xcode 7.3 on OS X 10.11, Xcode 8.3 on macOS 10.12,
On 26 March 2018 at 00:14, Rainer Müller wrote:
> On 2018-03-25 06:11, Ryan Schmidt wrote:
>>
>> Currently PRs are tested by a separate build infrastructure on Travis. It
>> runs on three systems: Xcode 7.3 on OS X 10.11, Xcode 8.3 on macOS 10.12,
>> and Xcode 9.3beta on macOS 10.13. These builds
On 2018-03-25 06:11, Ryan Schmidt wrote:
>
> On Mar 24, 2018, at 18:41, Michael Dickens wrote:
>
>> The only other "gotcha" I wonder about is including buildbots for various
>> target OSs [do PRs already go through building on (say) 10.6 and newer?]
>
> The Buildbot is not currently involved in
Hi Ryan,
I would just like to point out regarding testsuites that it can sometimes
happen in my experience for the test phase to fail because of a problem in
packaging rather than an inherent problem in the source. For example,
something wasn't linked properly, and the way a library was passed to
On Mar 24, 2018, at 18:41, Michael Dickens wrote:
> The only other "gotcha" I wonder about is including buildbots for various
> target OSs [do PRs already go through building on (say) 10.6 and newer?]
The Buildbot is not currently involved in doing builds of PRs. There has been
discussion on t
On Mar 24, 2018, at 16:06, Perry E. Metzger wrote:
> It occurs to me that
>
> 1) Some ports have "livecheck", which is automated detection that an
> updated source file is available.
> 2) Some ports have "port test" automated testing available (though not
> many.)
>
> It might therefore be
I like the idea, generally. The vast majority of my updates could be automated
in this manner. There will always be a few that need patching or tweaks to
existing patches, which will have to be done by hand. The only other "gotcha" I
wonder about is including buildbots for various target OSs [do
It occurs to me that
1) Some ports have "livecheck", which is automated detection that an
updated source file is available.
2) Some ports have "port test" automated testing available (though not
many.)
It might therefore be interesting (though not a small amount of work)
to set something up
