Le dim. 13 août 2023, 16:57, Frédéric Martinsons < frederic.martins...@gmail.com> a écrit :
> > > On Sun, 13 Aug 2023 at 15:09, Richard Purdie < > richard.pur...@linuxfoundation.org> wrote: > >> On Sun, 2023-08-13 at 12:22 +0100, Richard Purdie via >> lists.openembedded.org wrote: >> > On Sun, 2023-08-13 at 12:48 +0200, Frédéric Martinsons wrote: >> > > >> > > >> > > Le dim. 13 août 2023, 12:23, Richard Purdie >> > > <richard.pur...@linuxfoundation.org> a écrit : >> > > > On Sun, 2023-08-13 at 10:23 +0200, Frederic Martinsons wrote: >> > > > > From: Frederic Martinsons <frederic.martins...@gmail.com> >> > > > > >> > > > > This is an RFC for introducing a new class and recipes that >> > > > > help building C-ABI compatible header and library around >> > > > > rust code. >> > > > > >> > > > > The third patch add examples and test to demonstrate >> > > > > the usage and the good working of this use case. >> > > > > >> > > > > Test have been passed with the following in local.conf: >> > > > > >> > > > > CORE_IMAGE_EXTRA_INSTALL:append = " openssh-sshd openssh-scp >> > > > > cargo rust rust-c-lib-example-bin" >> > > > > IMAGE_CLASSES += "testimage" >> > > > > TEST_SUITES = "ping ssh rust" >> > > > > # To use slirp option in testimage.bbclass >> > > > > TEST_RUNQEMUPARAMS = "slirp" >> > > > > TEST_SERVER_IP = "127.0.0.1" >> > > > > QEMU_USE_SLIRP = "1" >> > > > >> > > > In testing it showed: >> > > > >> > > > stdio: WARNING: cargo-c-0.9.18-r0 do_recipe_qa: QA Issue: Recipe >> > > > cargo-c in /home/pokybuild/yocto-worker/a-full/build/meta/recipes- >> > > > devtools/rust/cargo-c_0.9.18.bb does not contain a SUMMARY. Please >> > > > add an entry. [missing-metadata] >> > > > stdio: WARNING: cargo-c-native-0.9.18-r0 do_recipe_qa: QA Issue: >> > > > Recipe cargo-c in /home/pokybuild/yocto-worker/a- >> > > > full/build/meta/recipes-devtools/rust/cargo-c_0.9.18.bb does not >> > > > contain a SUMMARY. Please add an entry. [missing-metadata] >> > > > stdio: WARNING: nativesdk-cargo-c-0.9.18-r0 do_recipe_qa: QA Issue: >> > > > Recipe cargo-c in /home/pokybuild/yocto-worker/a- >> > > > full/build/meta/recipes-devtools/rust/cargo-c_0.9.18.bb does not >> > > > contain a SUMMARY. Please add an entry. [missing-metadata] >> > > >> > > Thanks Richard, will take care of that soon. >> > > >> > > Can you tell me what commands do you run to have that sanity check? >> > > It will avoid me to do the same mistake next time I'll add a recipe. >> > >> > It should just show up building the recipe (e.g. "bitbake cargo-c")? >> > >> > There are further build failures: >> > >> > >> https://autobuilder.yoctoproject.org/typhoon/#/builders/101/builds/6361/steps/14/logs/stdio >> > >> https://autobuilder.yoctoproject.org/typhoon/#/builders/110/builds/6484/steps/14/logs/stdio >> > >> > and the build isn't finished yet so Is suspect there will be more. >> >> >> https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/5606/steps/15/logs/stdio >> >> not all of those failures are your patches but: >> >> 2023-08-13 12:38:57,894 - oe-selftest - INFO - >> ====================================================================== >> 2023-08-13 12:38:57,894 - oe-selftest - INFO - FAIL: >> distrodata.Distrodata.test_maintainers (subunit.RemotedTestCase) >> 2023-08-13 12:38:57,894 - oe-selftest - INFO - >> ---------------------------------------------------------------------- >> 2023-08-13 12:38:57,894 - oe-selftest - INFO - >> testtools.testresult.real._StringException: Traceback (most recent call >> last): >> File >> "/home/pokybuild/yocto-worker/oe-selftest-centos/build/meta/lib/oeqa/selftest/cases/distrodata.py", >> line 115, in test_maintainers >> self.fail(""" >> File >> "/home/pokybuild/yocto-worker/oe-selftest-centos/build/buildtools/sysroots/x86_64-pokysdk-linux/usr/lib/python3.11/unittest/case.py", >> line 703, in fail >> raise self.failureException(msg) >> AssertionError: >> Unable to find recipes for the following entries in maintainers.inc: >> rust-c-lib-example >> rust-c-lib-example-bin >> > > I don't understand these, because rust-c-lib-example and > rust-c-lib-example-bin have been added by PATCHV2 (3/4) in meta-selftest. > ./meta-selftest/recipes-devtools/rust/rust-c-lib-example-bin_git.bb > ./meta-selftest/recipes-devtools/rust/rust-c-lib-example_git.bb > > Is this because they are in meta-selftest ? Should I remove them from > maintainers.inc ? > > >> and this: >> >> Traceback (most recent call last): >> File >> "/home/pokybuild/yocto-worker/oe-selftest-centos/build/meta/lib/oeqa/core/decorator/__init__.py", >> line 35, in wrapped_f >> return func(*args, **kwargs) >> ^^^^^^^^^^^^^^^^^^^^^ >> File >> "/home/pokybuild/yocto-worker/oe-selftest-centos/build/meta/lib/oeqa/core/decorator/__init__.py", >> line 35, in wrapped_f >> return func(*args, **kwargs) >> ^^^^^^^^^^^^^^^^^^^^^ >> File >> "/home/pokybuild/yocto-worker/oe-selftest-centos/build/meta/lib/oeqa/runtime/cases/rust.py", >> line 31, in test_rust_compile >> self.assertEqual(status, 0, msg=msg) >> AssertionError: 127 != 0 : rust compile failed, output: sh: rustc: not >> found >> >> I don't understand this one either, I simply add openssh-scp in require > package to run test_rust_compile since its setup function > copy source on target via scp, rustc is provided by rust recipe and rust > recipe is required to run this test. Any ideas ? > In fact, I do know where it's come from, I just had to look for the docstring of the decorator OEHasPackage since it tells that the writing @OEHasPackage(['rust', 'openssh-scp']) means an "or" (test needs rust or openssh-scp), this is the wrong usage since the test needs both. The V3 of the series I just sent should correct that, I also make cargo-c purely native but for the maintainers.inc issue, I have no clue... > >> probably is are, so 2 of the 6 failures. The other 4 are "mine" :/. >> >> Cheers, >> >> Richard >> >>
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#186077): https://lists.openembedded.org/g/openembedded-core/message/186077 Mute This Topic: https://lists.openembedded.org/mt/100715215/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
