From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: svsvenss@cisco.com,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Cc: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Subject: Re: [bitbake-devel] [PATCH v2] fetch2/wget: reuse cached HTTPS connections
Date: Fri, 14 Aug 2026 22:24:51 +0100 [thread overview]
Message-ID: <2a1dfb64170ef90dde4f5def6fe7d86f720257f6.camel@linuxfoundation.org> (raw)
In-Reply-To: <DM6PR11MB396271299B36AB33F27D6BE2CBDA2@DM6PR11MB3962.namprd11.prod.outlook.com>
On Fri, 2026-08-14 at 20:12 +0000, Fredrik Svensson via lists.openembedded.org wrote:
> The failure happens while the new self-test is generating its
> temporary certificate, before it exercises the HTTPS connection
> cache. Unfortunately, the test currently redirects both stdout and
> stderr to /dev/null, so the log only contains the exit status.
>
> I reproduced the command in an AlmaLinux 8 container using the same
> Yocto 5.1 buildtools, where it succeeds. This therefore looks
> specific to the alma8-vk-2worker, possibly its crypto/FIPS
> configuration or local state.
>
> I will prepare a small follow-up patch which captures the OpenSSL
> output and includes it in the log. A rerun with that patch should
> expose the actual reason.
Thanks, I applied it and the result was:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4383/steps/15/logs/stdio
which suggests buildtools isn't working quite right. What is odd is
that if I ssh in and run that bitbake-selftest command on the same
build directory, it works and doesn't show the error. I'm not quite
sure what is going on here...
Cheers,
Richard
next prev parent reply other threads:[~2026-08-14 21:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 17:03 [PATCH v2] fetch2/wget: reuse cached HTTPS connections Fredrik Svensson (svsvenss)
2026-08-14 13:21 ` [bitbake-devel] " Richard Purdie
2026-08-14 20:12 ` Fredrik Svensson (svsvenss)
2026-08-14 21:24 ` Richard Purdie [this message]
2026-08-17 6:55 ` Fredrik Svensson (svsvenss)
2026-08-17 14:07 ` Richard Purdie
2026-08-17 13:48 ` chris.laplante
2026-08-17 14:14 ` Fredrik Svensson (svsvenss)
2026-08-17 14:17 ` chris.laplante
2026-08-17 19:34 ` [bitbake-devel] " Richard Purdie
2026-08-17 19:36 ` chris.laplante
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=2a1dfb64170ef90dde4f5def6fe7d86f720257f6.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=svsvenss@cisco.com \
/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.