From: Babanpreet Singh <bbnpreetsingh@gmail.com>
To: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Cc: bitbake-devel@lists.openembedded.org,
Babanpreet Singh <bbnpreetsingh@gmail.com>
Subject: Re: [PATCH] cooker: create missing eventlog directory
Date: Sat, 14 Nov 2026 18:55:40 +0000 [thread overview]
Message-ID: <20261114185540.7-1-bbnpreetsingh@gmail.com> (raw)
In-Reply-To: <20261113-mathieu-b16492-write-variables-v1-1-9f1f86aebc8b@bootlin.com>
On Fri, 13 Nov 2026 at 15:34 +0100, Mathieu Dubois-Briand wrote:
> If the eventlog folder is removed while bitbake is still resident in
> memory, it will not be re-created on the next build and result in an
> exception while trying to write event logs. Catch this exception and
> create the folder as expected.
>
> [YOCTO #16492]
>
> Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
The steps from the bug pass here with this applied.
Tested-by: Babanpreet Singh <bbnpreetsingh@gmail.com>
Baban
prev parent reply other threads:[~2026-11-14 18:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 14:34 [PATCH] cooker: create missing eventlog directory Mathieu Dubois-Briand
2026-11-14 18:55 ` Babanpreet Singh [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=20261114185540.7-1-bbnpreetsingh@gmail.com \
--to=bbnpreetsingh@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=mathieu.dubois-briand@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox