Andrey Semashev wrote:
On 11/6/23 14:30, Peter Dimov via Boost wrote:
John Maddock wrote:
A typical example - clang on ubuntu jammy just stopped working - the cause was an update of the system default compiler from gcc-12 to gcc-13 which rendered the clang version we were testing non-functional. The solution is to do what you would tell a user to do - update the clang version to one that can handle gcc-13's std lib!
Or just use the ubuntu:22.04 container instead of GHA's image.
Given that the GHA images break something every so often, I'm starting to think that we should just use containers for everything and isolate ourselves from the changes in the base images.
I suspect, Docker has its overhead. Apart from downloading the Docker image (is it cached? who knows), setting it up for testing usually requires installation of more packages. Furthermore, I'm not sure if that package downloading is backed by GHA cache (probably not), which means you're pulling packaged from Ubuntu repos instead of the GHA local cache, which is configured in the GHA images. I don't need to remind you that network issues often cause spurious CI failures, which means the less network activity the better.
That's why I've been (irrationally) avoiding containers as much as possible, but I suspect that none of the above is true in practice.