From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <adam.duskett@amarulasolutions.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v12 1/4] libtoml1: fix building tests with gcc 16
Date: Thu, 05 Nov 2026 19:13:04 +0100 [thread overview]
Message-ID: <DMNHBMHYU9DA.39FGYAZSDM7NX@bootlin.com> (raw)
In-Reply-To: <20261104132057.607953-1-adam.duskett@amarulasolutions.com>
On Wed Nov 4, 2026 at 2:20 PM CET, Adam Duskett via openembedded-core wrote:
> GCC 16 warns that the format may be used uninitialized when a value is
> assigned a different type, for example:
>
> toml::value v(true);
> v = std::chrono::hours(1);
>
> The warning is a false positive, but the tests build with -Werror, so
> the build fails.
>
> Every operator= copied the old format out of the union behind a type
> check that GCC could not see through, so it flagged a possible read of
> an inactive member.
>
> Add a small helper that keeps the format when the type is unchanged and
> uses the default format otherwise, so the old format is never copied.
> The convenience overloads now convert their argument and forward to the
> main ones, removing a lot of duplicated code.
>
> Fixes:
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/40/builds/4814
>
> Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
> ---
Hi Adam,
Thanks for the new version. It looks better, with only one selftest
failure, only on ARM hosts.
2026-11-05 09:43:06,955 - oe-selftest - INFO - fitimage.KernelFitImageRecipeTests.test_fit_image_sign_initramfs_bundle (subunit.RemotedTestCase)
2026-11-05 09:43:06,956 - oe-selftest - INFO - ... FAIL
...
2026-11-05 09:43:06,956 - oe-selftest - INFO - 14: 8/74 452/795 (183.10s) (0 failed) (fitimage.KernelFitImageRecipeTests.test_fit_image_sign_initramfs_bundle)
2026-11-05 09:43:06,956 - oe-selftest - INFO - testtools.testresult.real._StringException: Traceback (most recent call last):
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/fitimage.py", line 1629, in test_fit_image_sign_initramfs_bundle
self._test_fitimage(bb_vars)
~~~~~~~~~~~~~~~~~~~^^^^^^^^^
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/fitimage.py", line 719, in _test_fitimage
fitimage_its_path, fitimage_path = self._bitbake_fit_image(bb_vars)
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/fitimage.py", line 828, in _bitbake_fit_image
bitbake(self.kernel_recipe)
~~~~~~~^^^^^^^^^^^^^^^^^^^^
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/utils/commands.py", line 247, in bitbake
return runCmd(cmd, ignore_status, timeout, output_log=output_log, **options)
File "/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/lib/oeqa/utils/commands.py", line 214, in runCmd
raise AssertionError("Command '%s' returned non-zero exit status %d:\n%s" % (command, result.status, exc_output))
AssertionError: Command 'bitbake linux-yocto-fitimage' returned non-zero exit status 1:
...
ERROR: linux-yocto-fitimage-1.0-r0 do_package_qa: QA Issue: File /boot/fitImage in package linux-yocto-fitimage contains reference to TMPDIR [buildpaths]
ERROR: linux-yocto-fitimage-1.0-r0 do_package_qa: Fatal QA errors were found, failing task.
ERROR: Logfile of failure stored in: /srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-1135637/tmp/work/qemuarm64-poky-linux/linux-yocto-fitimage/1.0/temp/log.do_package_qa.159937
NOTE: recipe linux-yocto-fitimage-1.0-r0: task do_package_qa: Failed
ERROR: Task (/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/layers/openembedded-core/meta/recipes-kernel/linux/linux-yocto-fitimage.bb:do_package_qa) failed with exit code '1'
https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/5224
I know this one might be a bit tricky to reproduce, as it only occurs on
ARM platforms. If you want to run some tests, I can schedule some builds
on the autobuilder.
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2026-11-05 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 13:20 [PATCH v12 1/4] libtoml1: fix building tests with gcc 16 Adam Duskett
2026-11-04 13:20 ` [PATCH v12 2/4] rpm: add 0017-critically-fail-if-post-install-fails.patch Adam Duskett
2026-11-04 13:20 ` [PATCH v12 3/4] dnf: Upgrade to 5.4.6.0 Adam Duskett
2026-11-04 13:20 ` [PATCH v12 4/4] libdnf: remove recipe Adam Duskett
2026-11-05 18:13 ` Mathieu Dubois-Briand [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DMNHBMHYU9DA.39FGYAZSDM7NX@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=adam.duskett@amarulasolutions.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.