Hi Richard
> > you can run these with commands like:
> >
> > os-selftest -r sstatetests.SStateTests.test_sstate_allarch_samesigs
One more question is that I executed os-selftest in my yocto build
environment, and it was passed. So how could I reproduce the error log?
/build$ oe-selftest -r sstatetests.SStateTests.test_sstate_allarch_samesigs
2019-09-17 11:11:40,703 - oe-selftest - INFO - Adding layer libraries:
2019-09-17 11:11:40,703 - oe-selftest - INFO -
/home/zhengrq/workdir/yotco/poky/meta/lib
2019-09-17 11:11:40,704 - oe-selftest - INFO -
/home/zhengrq/workdir/yotco/poky/meta-yocto-bsp/lib
2019-09-17 11:11:40,704 - oe-selftest - INFO -
/home/zhengrq/workdir/yotco/poky/meta-selftest/lib
2019-09-17 11:11:40,704 - oe-selftest - INFO -
/home/zhengrq/workdir/yotco/meta-openembedded/meta-oe/lib
2019-09-17 11:11:40,707 - oe-selftest - INFO - Running bitbake -e to test the
configuration is valid/parsable
2019-09-17 11:11:42,406 - oe-selftest - INFO - Adding: "include selftest.inc"
in /home/zhengrq/workdir/yotco/build/conf/local.conf
2019-09-17 11:11:42,407 - oe-selftest - INFO - Adding: "include bblayers.inc"
in bblayers.conf
2019-09-17 11:11:42,407 - oe-selftest - INFO - test_sstate_allarch_samesigs
(sstatetests.SStateTests)
2019-09-17 11:17:00,034 - oe-selftest - INFO - ... ok
2019-09-17 11:17:00,047 - oe-selftest - INFO -
----------------------------------------------------------------------
2019-09-17 11:17:00,047 - oe-selftest - INFO - Ran 1 test in 317.641s
2019-09-17 11:17:00,047 - oe-selftest - INFO - OK
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
fatal: not a git repository (or any of the parent directories): .git
2019-09-17 11:17:07,025 - oe-selftest - INFO - RESULTS:
2019-09-17 11:17:07,026 - oe-selftest - INFO - RESULTS -
sstatetests.SStateTests.test_sstate_allarch_samesigs: PASSED (317.64s)
2019-09-17 11:17:07,065 - oe-selftest - INFO - SUMMARY:
2019-09-17 11:17:07,065 - oe-selftest - INFO - oe-selftest () - Ran 1 test in
317.642s
2019-09-17 11:17:07,065 - oe-selftest - INFO - oe-selftest - OK - All required
tests passed (successes=1, skipped=0, failures=0, errors=0)
--------------------------------------------------
Zheng Ruoqin
Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
ADDR.: No.6 Wenzhu Road, Software Avenue,
Nanjing, 210012, China
MAIL : [email protected]
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of
> Zheng, Ruoqin
> Sent: Tuesday, September 17, 2019 8:45 AM
> To: [email protected]
> Subject: Re: [OE-core] [PATCH] dnf: make dnf work in toolchain
>
> Hi Richard
>
> > you can run these with commands like:
> >
> > os-selftest -r sstatetests.SStateTests.test_sstate_allarch_samesigs
> >
> > Cheers,
>
> Could you tell me what does the oe-selftest in here test for? Especially
> what do
> the signature tests test for?
>
> Thanks
> --------------------------------------------------
> Zheng Ruoqin
> Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
> ADDR.: No.6 Wenzhu Road, Software Avenue,
> Nanjing, 210012, China
> MAIL : [email protected]
>
>
> > -----Original Message-----
> > From: Richard Purdie [mailto:[email protected]]
> > Sent: Monday, September 16, 2019 6:57 PM
> > To: Zheng, Ruoqin/郑 若钦 <[email protected]>; openembedded-
> > [email protected]
> > Subject: Re: [OE-core] [PATCH] dnf: make dnf work in toolchain
> >
> > On Mon, 2019-09-16 at 14:36 +0800, Zheng Ruoqin wrote:
> > > We need to configure dnf to use package architecture from yocto
> > > build system.
> > >
> > > Install etc/dnf/vars to ${SDKTARGETSYSROOT} because config file in
> > > host-sysroot as /opt/poky/2.7+snapshot/sysroots/x86_64-pokysdk-linux
> > > will be covered by another ARCH which result in previous config
> > > settings inefficacy.
> > >
> > > To resolve it, put config file in target-sysroot like
> > > /opt/poky/2.7+snapshot/sysroots/core2-64-poky-linux. As each ARCH
> > > has its own target-sysroot, config file will not be covered.
> >
> > I'm afraid we can't have target dependencies within nativesdk packages.
> >
> > This is shown by the fact this patch (and the similar rpm one) cause
> > selftest failures in the signature tests:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/381/
> > steps/8
> > /logs/step2d
> >
> > 2019-09-16 00:24:54,670 - oe-selftest - INFO - RESULTS -
> > sstatetests.SStateTests.test_sstate_allarch_samesigs: FAILED (111.59s)
> > 2019-09-16 00:24:54,670 - oe-selftest - INFO - RESULTS -
> > sstatetests.SStateTests.test_sstate_nativesdk_samesigs_multilib:
> > FAILED
> > (144.14s)
> > 2019-09-16 00:24:54,670 - oe-selftest - INFO - RESULTS -
> > sstatetests.SStateTests.test_sstate_sametune_samesigs: FAILED
> > (161.53s)
> >
> > you can run these with commands like:
> >
> > os-selftest -r sstatetests.SStateTests.test_sstate_allarch_samesigs
> >
> > Cheers,
> >
> > Richard
> >
> >
>
>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> [email protected]
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
