From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Frederic Martinsons" <frederic.martinsons@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCHV2 0/3] Create class for building and installing rust tests
Date: Wed, 26 Apr 2023 23:10:29 +0200 [thread overview]
Message-ID: <20230426231029.6ae3c6af@booty> (raw)
In-Reply-To: <cover.1682341336.git.frederic.martinsons@gmail.com>
Hello Frederic,
On Mon, 24 Apr 2023 15:04:10 +0200
"Frederic Martinsons" <frederic.martinsons@gmail.com> wrote:
> From: Frederic Martinsons <frederic.martinsons@gmail.com>
>
> This brings the possibility to use this class to build and ship
> unit tests of rust projects, the class also create (or modified)
> standard run-ptest script to run the generated rust test suite.
>
> It has been tested successfully with core-image-sato under qemu
> for zvariant-ptest and python3-bcrypt-ptest (though the last one
> didn't define any unit tests).
>
> Note that I tried to do the same with python3-cryptography but fail
> to build the test suite and I don't know how to do it with the rust
> extension module build by python setuptools. There must be some kind
> of way for doing that so maybe someone will put some work in it (
> because python3-cryptography rust extension do have unit tests).
>
> Moreover, in the class, I didn't manage to share data between
> do_compile_ptest_base and do_install_ptest_base cleanly (I tried
> to d.setVar in compile and d.getVar in install but it seems that
> the data store doens't recognize my new variable) so I used a file
> for that. I'm sure there is a clever way for doing that, so feel
> free to tell me.
A build error appeared on the autobuilders with these patches applied:
File "/home/pokybuild/yocto-worker/oe-selftest-armhost/build/meta/lib/oeqa/selftest/cases/devtool.py", line 879, in test_devtool_modify_git_crates_subpath
self._test_recipe_contents(recipefile, {}, ['cargo'])
File "/home/pokybuild/yocto-worker/oe-selftest-armhost/build/meta/lib/oeqa/selftest/cases/devtool.py", line 169, in _test_recipe_contents
self.assertIn(inherit, inherits, 'Missing inherit of %s' % inherit)
File "/usr/lib/python3.8/unittest/case.py", line 1179, in assertIn
self.fail(self._formatMessage(msg, standardMsg))
File "/usr/lib/python3.8/unittest/case.py", line 753, in fail
raise self.failureException(msg)
AssertionError: 'cargo' not found in {'pkgconfig', 'cargo-update-recipe-crates', 'ptest-cargo'} : Missing inherit of cargo
Log:
https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/1321/steps/14/logs/stdio
Best regards,
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-04-26 21:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 13:04 [PATCHV2 0/3] Create class for building and installing rust tests frederic.martinsons
2023-04-24 13:04 ` [PATCHV2 1/3] ptest-cargo.bbclass: create class frederic.martinsons
2023-04-24 13:04 ` [PATCHV2 2/3] python3-bcrypt: enable build of unit tests frederic.martinsons
2023-04-24 13:04 ` [PATCHV2 3/3] zvariant: add ptest feature for zvariant test suite frederic.martinsons
2023-04-26 21:10 ` Luca Ceresoli [this message]
2023-04-27 4:42 ` [OE-core] [PATCHV2 0/3] Create class for building and installing rust tests Frédéric Martinsons
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230426231029.6ae3c6af@booty \
--to=luca.ceresoli@bootlin.com \
--cc=frederic.martinsons@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox