Collin Funk wrote:
> Now we should be able to catch errors quickly as things update, etc.
Right. With this multi-platform-CI is it now easier to add a unit test:
Just make sure that it follows the specification and works on two or three
platforms, commit it, and then we'll see (within a week at most) which
other platforms need tweaks.
> It would be nice to be able to trigger runs and help fix any failures.
> My GitHub is name is "collinfunk" [1].
OK. Thanks for volunteering.
> I'm not sure if you have any "rules" for the repository, but I think it
> is best to follow the standard Gnulib procedure. Send any meaningful
> patches on the list so others can comment. Simple stuff like updating an
> 'apt' invocation to install necessary packages, for example, can be done
> silently.
Yes and no. This mailing list has quite a wide audience. I don't want to
have lots of chatter about CI details on this list. Therefore, what belongs
on this list is:
- Discussion whether a certain failure is a platform bug, a Gnulib code
bug, a Gnulib test bug, or a CI bug — unless it's obvious.
- Major decisions, such as about adding another platform to the CI.
But for the rest, such as messages like "I'm starting to investigate
the NetBSD failure in the last run" or "do you know the package name
of the locales on Alpine Linux", we should better use private email.
If private email at some point does not work well, then we should better
create a separate mailing list.
Bruno
