I usually run a-full with poky checkout pointing to my package update branch, so all upgrades are there, and things can and do break and they get privately addressed before any patches are sent here.

The branch is here
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akanavin/package-version-updates

Just started such a build now:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2768

All of the things in the matrix are poky-based, except that one sato build definition which uses nodistro:
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder-helper/tree/config.json

If you see gaps in that config.json, they can be addressed. Adding world to the nodistro build is an option.

Alex

On Mon, 18 Oct 2021 at 16:54, Martin Jansa <martin.jansa@gmail.com> wrote:
So you're testing your version upgrades by a build which doesn't include the upgraded recipes?

and that's the proof that "the upgrade works as intended" and then you get angry, because someone reports an regression and even sends a fix for it.. it's early, but I guess I need more coffee or beer to understand this.

FWIW: I'm not going to continue in this discussion before I calm down.

On Mon, Oct 18, 2021 at 4:45 PM Alexander Kanavin <alex.kanavin@gmail.com> wrote:
On Mon, 18 Oct 2021 at 16:38, Martin Jansa <martin.jansa@gmail.com> wrote:

I do test all my upgrades on the AB. For major ones like python or openssl, I run meta-oe builds too.

If the AB gives a green pass (which it did), then the upgrade works as intended. If you think AB is not doing enough testing, find the gaps in the AB matrix and address them.

 nodistro build with default oe-core setup obviously isn't covered by AB.

nodistro core-image-sato build is there, but not world. Sato doesn't include webkit:


Alex