On Fri, 2024-01-26 at 16:18 +0200, Mikko Rapeli wrote:
> Hi,
>
> On Fri, Jan 26, 2024 at 02:04:18PM +, 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,
They're forbidden in selftests as a whole, for other reasons. You can
probably find the reasons out via git blame.
Alex
On Fri, 26 Jan 2024 at 16:14, Joakim Tjernlund
wrote:
>
> On Fri, 2024-01-26 at 15:55 +0100, Alexander Kanavin wrote:
> > On Fri, 26 Jan 2024 at 15:52, Joakim Tjernlund
> >
On Fri, 2024-01-26 at 15:55 +0100, Alexander Kanavin wrote:
> On Fri, 26 Jan 2024 at 15:52, Joakim Tjernlund
> wrote:
> > A thought just occurred to me, these vars(SANITY_TESTED_DISTROS,
> > buildhistory etc.),
> > do they need to be off in the original machine when building up the SSTATE ?
> >
On Fri, 26 Jan 2024 at 15:52, Joakim Tjernlund
wrote:
> A thought just occurred to me, these vars(SANITY_TESTED_DISTROS, buildhistory
> etc.),
> do they need to be off in the original machine when building up the SSTATE ?
> I figured they just needed to be off for the repro build(in -st dir)
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
> 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
Hi,
On Fri, Jan 26, 2024 at 02:04:18PM +, 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
> > wrote:
> > > I will try workaround these somehow
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
> 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
On Fri, 26 Jan 2024 at 14:21, Joakim Tjernlund
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.
On Fri, 2024-01-26 at 13:18 +0100, Alexander Kanavin wrote:
> On Fri, 26 Jan 2024 at 12:09, Joakim Tjernlund via
> lists.openembedded.org
> wrote:
> > These are hardcoded settings too of which some could need need tewaking,
> > DISTRO_FEATURES for sure.
> >
> > So reproducible builds does not
On Fri, 26 Jan 2024 at 12:09, Joakim Tjernlund via
lists.openembedded.org
wrote:
> These are hardcoded settings too of which some could need need tewaking,
> DISTRO_FEATURES for sure.
>
> So reproducible builds does not seem usable outside poky or am I missing
> something here ?
That is not
In poky/meta/lib/oeqa/selftest/context.py there is:
if "buildhistory.bbclass" in self.tc.td["BBINCLUDED"]:
self.tc.logger.error("You have buildhistory enabled already and
this isn't recommended for selftest, please disable it first.")
raise OEQAPreRun
if
11 matches
Mail list logo
