Re: [OE-core] oe-selftest reproducible.ReproducibleTests.test_reproducible_builds appears to hardcode important tunable params

[Mikko Rapeli <mikko.rapeli@linaro.org>]

Hi,

On Fri, Jan 26, 2024 at 02:04:18PM +0000, Joakim Tjernlund via lists.openembedded.org wrote:
> On Fri, 2024-01-26 at 14:33 +0100, Alexander Kanavin via lists.openembedded.org wrote:
> > On Fri, 26 Jan 2024 at 14:21, Joakim Tjernlund
> > <Joakim.Tjernlund@infinera.com> wrote:
> > > I will try workaround these somehow but will not go so far as creating a new MACHINE just to
> > > run these tests.
> > 
> > Why would you need a new machine? You only need a new configuration
> > template in addition to existing one (e.g.
> > conf/templates/repro-test/local.conf.sample and bblayer.conf.sample).
> > Then initialize the build with TEMPLATECONF pointing to that.
> 
> Ah, there is an idea. But this will still change the original machine so one cannot switch
> between normal builds and repro builds in he same tree.

FWIW, I ran into the same issues. Many selftests also have dependencies which only work
on pure poky distro, machine and build configs. The dependencies to various features
which break tests are not clearly marked inside the tests.

At least with repro test it is now possible to define different image and recipe
build targets instead of world builds now but sadly these tests can not be run on
real product machine configurations and need a vanilla poky machine and/or distro
configs. I guess patches welcome but not sure into which direction...

Cheers,

-Mikko