From: Alper Nebi Yasak <alpernebiyasak@gmail.com>
To: Tom Rini <trini@konsulko.com>
Cc: Simon Glass <sjg@chromium.org>, u-boot@lists.denx.de
Subject: Re: binman and faked blobs failures
Date: Sat, 16 Apr 2022 20:30:12 +0300 [thread overview]
Message-ID: <b73b33c0-f04b-ed25-a5f1-f51ec9d55b03@gmail.com> (raw)
In-Reply-To: <20220411212830.GC14282@bill-the-cat>
On 12/04/2022 00:28, Tom Rini wrote:
> [...]
>
> Note that nothing changed for the board but on the second build now the
> faked blob is unhappy and causes a failure message that I don't see the
> first time, and probably shouldn't see this time either? This is a
> problem for me in that it's on most x86 boards and so makes it easier to
> miss other real build failures in my testing.
Yeah, the root cause here is that fake files created in the first build
are interpreted as actual files in subsequent builds. Simon already
added a TODO in binman.rst for cleaning them up, I intend to give it a
try but didn't have the time to experiment.
next prev parent reply other threads:[~2022-04-16 17:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 21:28 binman and faked blobs failures Tom Rini
2022-04-16 17:30 ` Alper Nebi Yasak [this message]
2022-04-19 21:54 ` Simon Glass
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=b73b33c0-f04b-ed25-a5f1-f51ec9d55b03@gmail.com \
--to=alpernebiyasak@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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.