Re: 回复: [edk2-devel] [PATCH v2 00/13] BaseTools,CryptoPkg,MdePkg,OvmfPkg: Delete CLANG35,CLANG38,GCC48,GCC49, rename GCC5 to GCC, update CLANGDWARF, delete VS 2008-2013, EBC

["Gerd Hoffmann" <kraxel@redhat.com>]

> Given it's catching issues, I'd like to keep it too.
> 
> In terms of CI coverage, I'd like to have both gcc 6 and gcc 12 running GCC
> and GCCNOLTO builds: we've already broken gcc 5 compatibility by introducing
> GoogleTest (which uses nullptr), so by doing builds with gcc 6 we'll be able
> to know when we break it and update tools_def.txt.template with a note that
> we'll subsequently require gcc 7.

So you want gcc-6 specifically or just an older version instead of
latest?  I could try add a RHEL-8 container (which ships gcc-8).

> Similarly, we should also add CLANGPDB and CLANGDWARF builds.

Fedora ships clang + llvm (version 15.0.7 right now), so adding that
to the CI container should be easy.

> I suspect we'll rapidly run into scaling issues though, since GitHub Actions
> has a limit of 20 concurrent jobs on the free plan (https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration),
> and in order to keep CI times reasonable we'll probably want many more tasks
> to be running in parallel.

Well, I've wondered whenever it makes sense to do _less_ stuff in
parallel, to get down the constant overhead (clone repos etc).
Especially with a limit on parallel jobs that could be faster
in the end ...

take care,
  Gerd