Run rt specific test in "core-image-rt" #patch #yocto #qemu #dunfell #linux


Nikita Gupta
 

Thanks Alexander,

For guiding me in the right way. I did the same and was able to do testing my image previously all of those tests were skipping but now some of them are passing and some of the status are unknown and skipped and i am trying to figure out the reason of the "unknown" status. Hope so sooner I will get the reason and solution as well.

Thanks for helping me.


Alexander Kanavin
 

You can simply open the recipe file for core-image-rt (in poky/meta)
to see what it does. The realtime-ness (of any image) is set by
setting PREFERRED_PROVIDER_virtual/kernel to the realtime flavour,
which you already did, and so core-image-full-cmdline will be just as
realtime as this one.

We do not have a lot of automated testing for the realtime behaviour,
as it is difficult to control in a qemu based virtual environment.
There's basically just poky/meta/lib/oeqa/runtime/cases/rt.py

If you want to check timings, etc. you will have to most likely put
the image on real hardware, and experiment with running tests and
utilities from command line. Then you can think of how to automate
them.

It would help if you describe your overall goal.

Alex

On Tue, 4 Oct 2022 at 21:21, Nikita Gupta <nikitagupta2509@...> wrote:

Hello Alexander

But core-image-full-cmdline is not going to give real time exposure, isn't it? The requirement is to make real time image so core-image-full-cmdline will satisfy the requirement?

And would i need to run test of rt-suit one-by one or there is something so i can run in one go? Can you refer me some documents in which I get all these information as I didn't find all these info in one document.

As I am new in this thing please guide me . Your guidance is highly appreciated.



On Tue, Oct 4, 2022, 18:31 Alexander Kanavin <alex.kanavin@...> wrote:

The log file seems truncated?

To enable the standard rt test, use

TEST_SUITES:append = ' rt'

as seen in https://git.yoctoproject.org/yocto-autobuilder-helper/tree/config.json#n1138

and build core-image-full-cmdline. core-image-rt is not well tested
unfortunately.

Alex

On Sun, 2 Oct 2022 at 16:15, Nikita Gupta <nikitagupta2509@...> wrote:

Hello Alexander,

Please find log.do_rootfs file for the image.


Nikita Gupta
 

Hello Alexander

But core-image-full-cmdline is not going to give real time exposure, isn't it?  The requirement is to make real time image so core-image-full-cmdline will satisfy the requirement?

And would i need to run test of rt-suit one-by one or there is something so i can run in one go? Can you refer me some documents in which I get all these information as I didn't find all these info in one document.

As I am new in this thing please guide me . Your guidance is highly appreciated.



On Tue, Oct 4, 2022, 18:31 Alexander Kanavin <alex.kanavin@...> wrote:
The log file seems truncated?

To enable the standard rt test, use

TEST_SUITES:append = ' rt'

as seen in https://git.yoctoproject.org/yocto-autobuilder-helper/tree/config.json#n1138

and build core-image-full-cmdline. core-image-rt is not well tested
unfortunately.

Alex

On Sun, 2 Oct 2022 at 16:15, Nikita Gupta <nikitagupta2509@...> wrote:
>
> Hello Alexander,
>
> Please find log.do_rootfs file for the image.
>
>


Alexander Kanavin
 

The log file seems truncated?

To enable the standard rt test, use

TEST_SUITES:append = ' rt'

as seen in https://git.yoctoproject.org/yocto-autobuilder-helper/tree/config.json#n1138

and build core-image-full-cmdline. core-image-rt is not well tested
unfortunately.

Alex

On Sun, 2 Oct 2022 at 16:15, Nikita Gupta <nikitagupta2509@...> wrote:

Hello Alexander,

Please find log.do_rootfs file for the image.


Nikita Gupta
 

Hello Alexander, 

Please find log.do_rootfs file for the image.  


Alexander Kanavin
 

It helps if you show log.do_rootfs for the image, so it's possible to
inspect what actually got installed into it.

Alex

On Sun, 2 Oct 2022 at 09:29, Nikita Gupta <nikitagupta2509@...> wrote:

Hello All,

I have made a preempt-rt image with "core-image-rt" by including the following line in local.conf file.

PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"
IMAGE_CLASSES += "testimage testsdk"
EXTRA_IMAGE_FEATURES = ptest-pkgs debug-tweaks"

and the bake my recipe with following command.

bitbake core-image-rt

I got my image successfully ready. Now I want to do testing of this image so I run the following command .

bitbake core-image-rt -c testimage

So i am seeing my all tests are skipped ( attached ). Kindly make me clear on following points .
1. Why my all tests are skipped?
2. How can I run the rt-specific test in my image? Except cyclictest any test, i need to run for this particular image ?
3. Would I need to run every test individually through bitbake or any other specific command so my p-test would run?
3. How can I generate the test report?

Any replies would be helpful for me. Thanks in advance


Nikita Gupta
 

Hello All, 

I have made a preempt-rt image with "core-image-rt" by including the following line in local.conf file. 

PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"
IMAGE_CLASSES += "testimage testsdk"
EXTRA_IMAGE_FEATURES = ptest-pkgs debug-tweaks"

and the bake my recipe with following command.

bitbake core-image-rt

I got my image successfully ready. Now I want to do testing of this image so I run the following command .

bitbake core-image-rt -c testimage 

So i am seeing my all tests are skipped ( attached ). Kindly make me clear on following points .
1. Why my all tests are skipped?
2. How can I run the rt-specific test in my image? Except cyclictest any test, i need to run for this particular image ?
3. Would I need to run every test individually through bitbake or any other specific command so my p-test would run?
3. How can I generate the test report?

Any replies would be helpful for me. Thanks in advance