Signed-off-by: Aníbal Limón <anibal.limon@...> --- tests/toaster/__init__.py | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/tests/toaster/__init__.py

The stop method have force mode because toaster without production setup have known issues when is on load, the server response 503 service unavailable. This mode iterates over process to found PID's

In order to provide a better interface add a ToasterHelper class the functionality is the same so only modified functions to match method definitions. Signed-off-by: Aníbal Limón

When call toaster_start on failing scenarios (already started) it becomes blocked on process.communicate() function so add my own function for solve this issue. The new function uses a tempfile

From: Aníbal Limón <limon.anibal@...> Bash interactive mode isn't useful so remove it. Signed-off-by: Aníbal Limón <limon.anibal@...> --- tests/toaster/helpers.py | 6 +++--- 1 file

From: Aníbal Limón <limon.anibal@...> The main idea is to have an script for execute tests against toaster so for now the arguments to execute toaster tests are fixed but will be configured

From: Aníbal Limón <limon.anibal@...> README.md: Toaster tests requires bash so add it. TODO is add a sanity module for test this kind of issues like shell compatibility. Signed-off-by:

From: Aníbal Limón <limon.anibal@...> A module in python will be created for have toaster helpers with clone, setup, start, stop. Signed-off-by: Aníbal Limón <limon.anibal@...> ---

From: Aníbal Limón <limon.anibal@...> Signed-off-by: Aníbal Limón <limon.anibal@...> --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md

This set of changes adds toaster test suite to qa-tools repo. Summary, - Add ToasterHelper class for clone/setup/start/stop toaster. - Add Toaster test suite script, mainly work did by QA Rumania

If you're using a postfunc you don't need to addtask at all: using postfuncs means you don't need to have a separate task at all. Ross

Cheers, mate! That solves my issue (but with small fix). do_unpack[postfuncs] += "do_latest_link" instead do_unpack[postfuncs] += "latest_link" Because, without

Digging deeper, I can see that versions 13 and 16 are in the linux-firmware source repository, so it is just a question of adding a package. I was already just adding the one firmware image I

Okay, solved it. It turned out that systemd was not in the image package. This separation between distro.conf and image.conf is little error-prone to me. But now it works. Greetings

I have been pondering linux-firmware recently too. I have a device fitted that requires the 'iwlwifi-7260' firmware. This was working but the current driver is requesting versions 13 to 10 of the

do_unpack[postfuncs] += "latest_link" will run latest_link after unpack has executed. Ross

Ok, but I don't want to run it everytime, just after the do_unpack. What I need to put it in requirements for each recipe ? Maybe something like do_unpack[require] = "latest_link" but I cannot find

Hello list, I am using wic to generate partitioned yocto images. After I boot such an Image, I see two added entrys in my /etc/fstab wich are not correct. cat /etc/fstab # # /etc/fstab: static file

Hello, I "activated" systemd as described in the development manual . My distro.conf (excerpt): When I build my distribution the following error appears while do_rootfs:

>So I wasn't quite right - I think you also need to come after do_packagedata and also you'll need to read the subpackage metadata. Inspired by insane.bbclass, this works: >addtask printrdeps