[OE-core] [PATCH] oeqa/selftest/kernel.py: Add new file destined for kernel related tests [YP#7202]: Test for linux-dummy The new kernel.py file is intended for kernel related test cases. The test for linux-dummy will ensure it is in good shape and...

[Constantin, Costin C]

Thanks Paul. Something happened to the commit message. I sent it previously to my e-mail and looked fine, but I guess I did something wrong in the  end.
I'll check as per your recommendations.

Cheers,

Costin 

-----Original Message-----
From: Paul Eggleton [mailto:paul.eggleton at linux.intel.com] 
Sent: Sunday, February 21, 2016 10:41 PM
To: Constantin, Costin C <costin.c.constantin at intel.com>
Cc: openembedded-core at lists.openembedded.org
Subject: Re: [OE-core] [PATCH] oeqa/selftest/kernel.py: Add new file destined for kernel related tests [YP#7202]: Test for linux-dummy The new kernel.py file is intended for kernel related test cases. The test for linux-dummy will ensure it is in good shape and...

Hi Costin,

On Sun, 21 Feb 2016 11:45:51 Costin Constantin wrote:
> Signed-off-by: Costin Constantin <costin.c.constantin at intel.com>

Commit messages should start with a "shortlog" (one line description of the
change) and then the commit message should be separated from that by a blank line so that it's not all crammed into the subject.

> ---
>  meta/lib/oeqa/selftest/kernel.py | 29 +++++++++++++++++++++++++++++
>  1 file changed, 29 insertions(+)
>  create mode 100644 meta/lib/oeqa/selftest/kernel.py
> 
> diff --git a/meta/lib/oeqa/selftest/kernel.py
> b/meta/lib/oeqa/selftest/kernel.py new file mode 100644 index 
> 0000000..3fe3517
> --- /dev/null
> +++ b/meta/lib/oeqa/selftest/kernel.py
> @@ -0,0 +1,29 @@
> +import os
> +import oeqa.utils.ftools as ftools
> +from oeqa.selftest.base import oeSelfTest from oeqa.utils.commands 
> +import runCmd, bitbake, get_bb_var from oeqa.utils.decorators import 
> +testcase
> +
> +class KernelTests(oeSelfTest):
> +    def  test_dummy_kernel(self):
> +        """
> +        [YP#7202]
> +        - test that linux-dummy target can be used as kernel provider 
> +for
> an image +        - check no "multiple providers are available for" message
> is received while building the image +        """
> +        config_param = 'PREFERRED_PROVIDER_virtual/kernel = "linux-dummy"'
> +        self.append_config(config_param)

Having set this, I would suggest verifying that it's actually taken effect, since it's common for this to be set within the distro/machine configuration.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre