Hello,

I feel that a-quick builds as they are have ceased to be quick or
lightweight, and I'd like to trim heavy items from them. The goal is
to:

- have a-quick complete in under an hour with fully populated sstate
- lessen the load on arm workers in particular; there is not enough of
them, and they should be used only in a-full
- make a-quick useful as a quick smoke check for patchsets that
reveals obvious issues rapidly, completes quickly, and doesn't compete
with a-full for resources too much. I would then be willing to use
them for that purpose.

The definitions of a-quick and a-full are here:
https://git.yoctoproject.org/yocto-autobuilder2/tree/config.py#n75

I'd like to make the following changes to reduce the load on arm workers:
- oe-selftest-armhost moves from shared to full. This is the biggest offender.

- qemuarm64-armhost does the same

There are also other heavy builds in a-quick that I think shouldn't be
a part of it:

- reproducible should move from shared to full. There's no way to make
it quicker.

- oe-selftest should be dropped from quick, or we could introduce
oe-selftest-quick that runs only a subset of sefltests that completes
under an hour (existing logs can be used to make that selection, e.g.
by tagging known slow test classes).

Thoughts?

Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62800): https://lists.yoctoproject.org/g/yocto/message/62800
Mute This Topic: https://lists.yoctoproject.org/mt/105041413/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to