From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Qi.Chen@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] oeqa/selftest: add test case to cover 'devtool modify -n' for a git recipe
Date: Fri, 26 Jan 2024 14:54:07 +0000 [thread overview]
Message-ID: <5b996521185e01326f83773135047dca0e946477.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240122052926.1962273-1-Qi.Chen@windriver.com>
On Mon, 2024-01-22 at 13:29 +0800, Chen Qi via lists.openembedded.org
wrote:
> From: Chen Qi <Qi.Chen@windriver.com>
>
> Add a test case to ensure the following error does not happen again for
> 'devtool modify -n'.
>
> Traceback (most recent call last):
> File "/buildarea2/chenqi/poky/scripts/devtool", line 349, in <module>
> ret = main()
> File "/buildarea2/chenqi/poky/scripts/devtool", line 336, in main
> ret = args.func(args, config, basepath, workspace)
> File "/buildarea2/chenqi/poky/scripts/lib/devtool/standard.py", line 924, in modify
> if not initial_revs["."]:
> KeyError: '.'
>
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
> meta/lib/oeqa/selftest/cases/devtool.py | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/meta/lib/oeqa/selftest/cases/devtool.py b/meta/lib/oeqa/selftest/cases/devtool.py
> index a877720769..22ea0ecba9 100644
> --- a/meta/lib/oeqa/selftest/cases/devtool.py
> +++ b/meta/lib/oeqa/selftest/cases/devtool.py
> @@ -917,6 +917,28 @@ class DevtoolModifyTests(DevtoolBase):
> # Try building
> bitbake(testrecipe)
>
> + def test_devtool_modify_git_no_extract(self):
> + # Check preconditions
> + testrecipe = 'psplash'
> + src_uri = get_bb_var('SRC_URI', testrecipe)
> + self.assertIn('git://', src_uri, 'This test expects the %s recipe to be a git recipe' % testrecipe)
> + # Clean up anything in the workdir/sysroot/sstate cache
> + bitbake('%s -c cleansstate' % testrecipe)
I'm afraid we can't use cleansstate inside oe-selftest as it may race
against other copies of oe-selftest running against the same sstate
cache (or other builds using psplash in this case).
We'll need to find another way to make this work.
Cheers,
Richard
next prev parent reply other threads:[~2024-01-26 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 5:29 [OE-core][PATCH] oeqa/selftest: add test case to cover 'devtool modify -n' for a git recipe Qi.Chen
2024-01-26 14:54 ` Richard Purdie [this message]
2024-01-26 15:00 ` Alexander Kanavin
2024-01-26 15:05 ` Richard Purdie
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=5b996521185e01326f83773135047dca0e946477.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Qi.Chen@windriver.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