[OE-core] [PATCH 1/1] pkgdata.py: avoid target-sdk-dummy-provides to mess things up
Sometimes we meet the following failure for the test_lookup_recipe test case. AssertionError: 'zlib\nbusybox is in the RPROVIDES of target-sdk-provid[32 chars]ummy' != 'zlib\nbusybox' zlib + busybox- busybox is in the RPROVIDES of target-sdk-provides-dummy: - target-sdk-provides-dummy This is because target-sdk-provides-dummy rprovides busybox. So clean things up to avoid failure. Signed-off-by: Chen Qi --- meta/lib/oeqa/selftest/cases/pkgdata.py | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/lib/oeqa/selftest/cases/pkgdata.py b/meta/lib/oeqa/selftest/cases/pkgdata.py index 0b4caf1..9911765 100644 --- a/meta/lib/oeqa/selftest/cases/pkgdata.py +++ b/meta/lib/oeqa/selftest/cases/pkgdata.py @@ -13,6 +13,7 @@ class OePkgdataUtilTests(OESelftestTestCase): super(OePkgdataUtilTests, cls).setUpClass() # Ensure we have the right data in pkgdata cls.logger.info('Running bitbake to generate pkgdata') +bitbake('target-sdk-provides-dummy -c clean') bitbake('busybox zlib m4') @OETestID(1203) -- 1.9.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 1/1] pkgdata.py: avoid target-sdk-dummy-provides to mess things up
On Tue, 2019-01-29 at 17:14 +0800, Chen Qi wrote: > Sometimes we meet the following failure for the test_lookup_recipe > test case. > > AssertionError: 'zlib\nbusybox is in the RPROVIDES of target-sdk- > provid[32 chars]ummy' != 'zlib\nbusybox' > zlib > + busybox- busybox is in the RPROVIDES of target-sdk-provides- > dummy: > - target-sdk-provides-dummy > > This is because target-sdk-provides-dummy rprovides busybox. > > So clean things up to avoid failure. > > Signed-off-by: Chen Qi > --- > meta/lib/oeqa/selftest/cases/pkgdata.py | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/meta/lib/oeqa/selftest/cases/pkgdata.py > b/meta/lib/oeqa/selftest/cases/pkgdata.py > index 0b4caf1..e02c6c4 100644 > --- a/meta/lib/oeqa/selftest/cases/pkgdata.py > +++ b/meta/lib/oeqa/selftest/cases/pkgdata.py > @@ -13,6 +13,7 @@ class OePkgdataUtilTests(OESelftestTestCase): > super(OePkgdataUtilTests, cls).setUpClass() > # Ensure we have the right data in pkgdata > cls.logger.info('Running bitbake to generate pkgdata') > +bitbake('target-sdk-provides-dummy -c cleansstate') > bitbake('busybox zlib m4') Nice debugging! clean is enough here, we don't want to run cleansstate on what might be a shared sstate cache though. Cheers, Richard -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/1] pkgdata.py: avoid target-sdk-dummy-provides to mess things up
Sometimes we meet the following failure for the test_lookup_recipe test case. AssertionError: 'zlib\nbusybox is in the RPROVIDES of target-sdk-provid[32 chars]ummy' != 'zlib\nbusybox' zlib + busybox- busybox is in the RPROVIDES of target-sdk-provides-dummy: - target-sdk-provides-dummy This is because target-sdk-provides-dummy rprovides busybox. So clean things up to avoid failure. Signed-off-by: Chen Qi --- meta/lib/oeqa/selftest/cases/pkgdata.py | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/lib/oeqa/selftest/cases/pkgdata.py b/meta/lib/oeqa/selftest/cases/pkgdata.py index 0b4caf1..e02c6c4 100644 --- a/meta/lib/oeqa/selftest/cases/pkgdata.py +++ b/meta/lib/oeqa/selftest/cases/pkgdata.py @@ -13,6 +13,7 @@ class OePkgdataUtilTests(OESelftestTestCase): super(OePkgdataUtilTests, cls).setUpClass() # Ensure we have the right data in pkgdata cls.logger.info('Running bitbake to generate pkgdata') +bitbake('target-sdk-provides-dummy -c cleansstate') bitbake('busybox zlib m4') @OETestID(1203) -- 1.9.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core