From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: yocto@lists.yoctoproject.org, alex.kanavin@gmail.com,
Ross Burton <Ross.Burton@arm.com>
Subject: Re: [yocto] make a-quick quick again (and light on the AB, particularly arm)
Date: Wed, 20 Mar 2024 12:13:38 +0000 [thread overview]
Message-ID: <f1afa9c5192e3a8b86686df4bec5bddc1280b346.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj8GNMB+=xkkzFW9iuX8Nk6fhC-XT3+3eY3thwK2tuZPCQ@mail.gmail.com>
On Wed, 2024-03-20 at 12:27 +0100, Alexander Kanavin wrote:
> On Wed, 20 Mar 2024 at 11:55, Ross Burton <Ross.Burton@arm.com>
> wrote:
> > I’d be against removing _all_ arm hosts from the quick build. With
> > the in-progress changes to the autobuilder hosting we should be
> > able to retire the slower Arm workers and a build running on the
> > Arm hosts shouldn’t be a problem. It would be a waste of effort to
> > attempt to optimise the build for the current cluster when there
> > are plans to relocate shortly anyway.
>
> Right, then let's not make this about arm builders, and simply drop
> selftest of any kind and reproducible from a-quick. How about that?
>
> Particularly selftest keeps getting bigger and slower and that isn't
> going to change. It used to take under an hour, nowadays it's 2+
> hours on x86 and 3+ on arm, with full sstate ready from the start.
It does depend what you're testing btw. You tend to test package
upgrades which don't really affect selftest as much as some of the
other changes I'm often dealing with.
I don't disagree with adding a separate target but I do want to make it
clear we should improve the speed of selftest too, I'm not ready to
give up on that yet!
Cheers,
Richard
next prev parent reply other threads:[~2024-03-20 12:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 9:33 make a-quick quick again (and light on the AB, particularly arm) Alexander Kanavin
2024-03-20 10:54 ` [yocto] " Ross Burton
2024-03-20 11:27 ` Alexander Kanavin
2024-03-20 12:13 ` Richard Purdie [this message]
2024-03-20 12:12 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f1afa9c5192e3a8b86686df4bec5bddc1280b346.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Ross.Burton@arm.com \
--cc=alex.kanavin@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).