[oe-selftest] adding new tests workflow

[oe-selftest] adding new tests workflow

[Igor Opaniuk]

Hi everyone,

I do have some questions about a standard workflow people usually
follow when adding new test sets to meta/lib/oeqa/selftest/cases/.

When oe-selftest is invoked for example this way:
oe-selftest --run-tests wic.Wic2.test_offset  --machine random

It usually creates a new build dir, then as far as I understood it
builds all available recipes (~30GB of build cache) for a random
machine.

When I try to invoke oe-selftest again, it prints error message that
build dir already exists:
2022-01-20 16:27:50,892 - oe-selftest - INFO - Adding layer libraries:
2022-01-20 16:27:50,892 - oe-selftest - INFO - openembedded-core.git/meta/lib
2022-01-20 16:27:50,892 - oe-selftest - INFO -
openembedded-core.git/meta-selftest/lib
2022-01-20 16:27:50,893 - oe-selftest - INFO - Running bitbake -e to
test the configuration is valid/parsable
2022-01-20 16:27:52,524 - oe-selftest - ERROR - Build directory
openembedded-core.git/build-st already exists, aborting

So there are two questions:
1. Are there a way to avoid building full set of recipes, if I really
want to run tests for one specific module (ksparser for example,
--run-tests wic)
2. Is it possible to re-use existing build directory for that and
expect bitbake to rebuild only recipes that were changed?

Thanks and looking forward to suggestions.

Regards,
Igor

-- 
Best regards - Freundliche Grüsse - Meilleures salutations

Igor Opaniuk
Embedded Software Engineer
T:  +380 938364067
E: igor.opaniuk@foundries.io
W: www.foundries.io

Re: [OE-core] [oe-selftest] adding new tests workflow

[Alexander Kanavin]

[-- Attachment #1: Type: text/plain, Size: 2484 bytes --]

You need to set your sstate cache directory to somewhere outside of the
build directory. Then the sstate cache will be reused between selftest
runs. The default behavior is to delete the selftest build directory if the
selftest succeeded, but the cache will ensure  that no long rebuilds will
be triggered.

Alex

On Thu, 20 Jan 2022 at 15:40, Igor Opaniuk <igor.opaniuk@foundries.io>
wrote:

> Hi everyone,
>
> I do have some questions about a standard workflow people usually
> follow when adding new test sets to meta/lib/oeqa/selftest/cases/.
>
> When oe-selftest is invoked for example this way:
> oe-selftest --run-tests wic.Wic2.test_offset  --machine random
>
> It usually creates a new build dir, then as far as I understood it
> builds all available recipes (~30GB of build cache) for a random
> machine.
>
> When I try to invoke oe-selftest again, it prints error message that
> build dir already exists:
> 2022-01-20 16:27:50,892 - oe-selftest - INFO - Adding layer libraries:
> 2022-01-20 16:27:50,892 - oe-selftest - INFO -
> openembedded-core.git/meta/lib
> 2022-01-20 16:27:50,892 - oe-selftest - INFO -
> openembedded-core.git/meta-selftest/lib
> 2022-01-20 16:27:50,893 - oe-selftest - INFO - Running bitbake -e to
> test the configuration is valid/parsable
> 2022-01-20 16:27:52,524 - oe-selftest - ERROR - Build directory
> openembedded-core.git/build-st already exists, aborting
>
> So there are two questions:
> 1. Are there a way to avoid building full set of recipes, if I really
> want to run tests for one specific module (ksparser for example,
> --run-tests wic)
> 2. Is it possible to re-use existing build directory for that and
> expect bitbake to rebuild only recipes that were changed?
>
> Thanks and looking forward to suggestions.
>
> Regards,
> Igor
>
> --
> Best regards - Freundliche Grüsse - Meilleures salutations
>
> Igor Opaniuk
> Embedded Software Engineer
> T:  +380 938364067
> E: igor.opaniuk@foundries.io
> W: www.foundries.io
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#160763):
> https://lists.openembedded.org/g/openembedded-core/message/160763
> Mute This Topic: https://lists.openembedded.org/mt/88559673/1686489
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [
> alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

[-- Attachment #2: Type: text/html, Size: 3498 bytes --]