Regarding github CI

[David Gilman]

If adding `port test` to the CI runner is not acceptable have you
considered setting up a second, separate buildbot/CI-type system for
this? You'd get a good signal from just running tests against a single
OS version, cutting down on the compute you need to do, and you'd only
open a PR once you've got a known good version update.

On Wed, Sep 6, 2023 at 5:01 PM Kirill A. Korinsky via macports-dev
<macports-dev at lists.macports.org> wrote:
>
> Folks,
>
> As you may have noticed a few weeks ago, I opened a PR https://github.com/macports/macports-ports/pull/20092 in which I propose enabling the execution of port test as part of GitHub's CI.
>
> I understand that not all ports currently have tests, but a lot of them does.
>
> My goal here is to enhance the quality of tests for the ports, which will allow me to proceed with a bot that runs `port livecheck...` and detects when ports are updated. Subsequently, it will open a PR to update a port with the updated version and checksums, but only if such a port has tests.
>
> Why? To automate the process of updating ports. We have a vast number of ports, and many of them can be updated quite easily. Enabling the execution of port tests on GitHub will ensure that such automatically generated PRs are of sufficient quality to be merged.
>
> What's the ultimate goal? To keep MacPorts dynamically updated.
>
> --
> wbr, Kirill
>


-- 
David Gilman
:DG<