Le lun. 27 juil. 2026 à 10:03, Nora Schiffer via lists.openembedded.org
<[email protected]> a écrit :

> On Sat, 2026-07-25 at 15:02 +0200, Mathieu Dubois-Briand wrote:
> > On Thu Jul 23, 2026 at 2:49 PM CEST, Nora Schiffer via
> lists.openembedded.org wrote:
> > > A similar feature was added in commit 9c8ef2119949 ("kernel-fit-image:
> > > control kernel section with FIT_LINUX_BIN") and subsequently reverted
> in
> > > commit 6eae261b6f52 ("Revert "kernel-fit-image: control kernel section
> > > with FIT_LINUX_BIN"") due to its incomplete implementation and lack of
> > > tests. Reintroduce an improved version:
> > >
> > > - The FIT_LINUX_BIN variable (which had been left unused) is renamed to
> > >   FIT_KERNEL_FILENAME. It can now actually be used to select a
> different
> > >   file from DEPLOY_DIR_IMAGE. The file will be compressed using
> > >   FIT_KERNEL_COMP_ALG as part of the FIT image recipe, rather than than
> > >   letting the kernel recipe handle this through
> > >   kernel-fit-extra-artifacts.bbclass.
> > > - Alternatively, FIT_KERNEL_FILENAME_COMPRESSED can be used to select a
> > >   pre-compressed file from DEPLOY_DIR_IMAGE. In this case,
> > >   FIT_KERNEL_COMP_ALG only controls the "compression" field of the
> > >   generated FIT image.
> > > - To preserve backwards compatibility, FIT_KERNEL_FILENAME_COMPRESSED
> > >   defaults to "linux.bin". As a special case, the compression algorithm
> > >   will be read from "linux_comp" for linux.bin. This behavior is
> > >   considered deprecated and relying on it results in a warning.
> > > - Add tests.
> > >
> > > To resolve the new deprecation warning, it is usually sufficient to set
> > > KERNEL_IMAGETYPE to the desired type ("Image" on many archs) and set
> > > FIT_KERNEL_FILENAME to the same value.
> > >
> > > Signed-off-by: Nora Schiffer <[email protected]>
> > > ---
> >
> > Hi Nora,
> >
> > Thanks for your patch.
> >
> > It looks like the test_fit_image_kernel_filename selftest is failing on
> > arm hosts:
>
> Hi Mathieu,
>
> I believe I know how to fix this, but it is unclear to me what exact
> configuration is built here. Is there any way I can replicate the same
> autobuilder configuration, so I can run the tests myself before submitting
> v2?
>

Hello,

You can find the generated config in the "Write Config" step just above the
failing step. In this case:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/4420/steps/14/logs/stdio

Regards,


>
> Best,
> Nora
>
>
>
> >
> > 2026-07-24 21:31:27,684 - oe-selftest - INFO -
> fitimage.KernelFitImageRecipeTests.test_fit_image_kernel_filename
> (subunit.RemotedTestCase)
> > 2026-07-24 21:31:27,685 - oe-selftest - INFO -  ... FAIL
> > ...
> > ERROR: linux-yocto-fitimage-1.0-r0 do_compile: Error executing a python
> function in exec_func_python() autogenerated:
> >
> > The stack trace of python calls that resulted in this exception/failure
> was:
> > File: 'exec_func_python() autogenerated', lineno: 2, function: <module>
> >      0001:
> >  *** 0002:do_compile(d)
> >      0003:
> > File:
> '/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/classes-recipe/kernel-fit-image.bbclass',
> lineno: 129, function: do_compile
> >      0125:
> >      0126:    elif kernel_compressed:
> >      0127:        kernel_path = os.path.join(kernel_deploydir,
> kernel_compressed)
> >      0128:        kernel_name = os.path.basename(kernel_compressed)
> >  *** 0129:        shutil.copyfile(kernel_path, kernel_name)
> >      0130:
> >      0131:    # FIT_KERNEL_FILENAME or FIT_KERNEL_FILENAME_COMPRESSED
> was set
> >      0132:    if kernel_name:
> >      0133:        root_node.fitimage_emit_section_kernel("kernel-1",
> kernel_name, kernel_comp_alg,
> > File: '/usr/lib/python3.14/shutil.py', lineno: 313, function: copyfile
> >      0309:
> >      0310:    if not follow_symlinks and _islink(src):
> >      0311:        os.symlink(os.readlink(src), dst)
> >      0312:    else:
> >  *** 0313:        with open(src, 'rb') as fsrc:
> >      0314:            try:
> >      0315:                with open(dst, 'wb') as fdst:
> >      0316:                    # macOS
> >      0317:                    if _HAS_FCOPYFILE:
> > Exception: FileNotFoundError: [Errno 2] No such file or directory:
> '/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-1142023/tmp/deploy/images/qemuarm64/bzImage'
> >
> > https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/4420
> >
> > Can you have a look at the issue?
> >
> > Thanks,
> > Mathieu
> >
>
> --
> TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
> Amtsgericht München, HRB 105018
> Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
> https://www.tq-group.com/
>
> 
>
>

-- 
Yoann Congal
Smile ECS
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#242060): 
https://lists.openembedded.org/g/openembedded-core/message/242060
Mute This Topic: https://lists.openembedded.org/mt/120409821/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to