On Mon, Dec 09, 2024 at 08:00:42AM -0700, Simon Glass wrote: > Hi Tom, > > On Sun, 8 Dec 2024 at 12:08, Tom Rini <[email protected]> wrote: > > > > First, introduce DEFAULT_ALL_TAG, DEFAULT_ARM64_TAG, DEFAULT_AMD64_TAG > > and DEFAULT_FAST_AMD64_TAG and remove the previous DEFAULT_TAG (as > > anyone making use of that will need to adjust their jobs). This allows > > us to say that some jobs can run on amd64 or arm64 hosts under the all > > tag, while some jobs must run on amd64 (the Xtensa jobs due to > > binary-only toolchains and sandbox for now) Then we rework the world > > build stage to only run on our very fast amd64 hosts, or our arm64 hosts > > (which are also very fast). This should result in a similar overall > > build time but also a much more consistent overall build time as we > > won't have the two big world jobs possibly run on our slower build > > nodes. > > > > Signed-off-by: Tom Rini <[email protected]> > > --- > > .gitlab-ci.yml | 74 ++++++++++++++++++-------------------------------- > > 1 file changed, 27 insertions(+), 47 deletions(-) > > I'd prefer fast_amd64 to avoid spaces
I don't see a reason to avoid spaces here. > What is the run time for this new, unified 'world' build? I just > wonder whether splitting it might make the runs go faster? It's about the same at the worst case of ~40-45min, but it's more consistent now, by excluding the older / slower amd64 hosts. -- Tom
signature.asc
Description: PGP signature
