From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Heiko Thiery <heiko.thiery@gmail.com>
Subject: Re: [PATCH 3/4] binman: Have faked binaries live in the output directory.
Date: Wed, 12 Jan 2022 15:03:11 -0500 [thread overview]
Message-ID: <20220112200311.GC9207@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ3cnVTtBqEurJ6S1FgOpUMYwfXuWHC7dh_5h7YxBJAR=w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
On Wed, Jan 12, 2022 at 01:01:17PM -0700, Simon Glass wrote:
> Hi Tom,
>
> On Tue, 11 Jan 2022 at 17:14, Tom Rini <trini@konsulko.com> wrote:
> >
> > In general, and for Azure specifically, we need to have files created in
> > the output directory and cannot assume a writable source directory.
> > Rework the faked blob support to put the faked binary in to the output
> > directory and then stop the test from deleting the now non-existent
> > file.
> >
> > Cc: Heiko Thiery <heiko.thiery@gmail.com>
> > Cc: Simon Glass <sjg@chromium.org>
> > Signed-off-by: Tom Rini <trini@konsulko.com>
> > ---
> > tools/binman/etype/blob.py | 4 +++-
> > tools/binman/ftest.py | 1 -
> > 2 files changed, 3 insertions(+), 2 deletions(-)
>
> Please see this:
>
> https://patchwork.ozlabs.org/project/uboot/patch/20220110031413.1970836-10-sjg@chromium.org/
Ah, I thought you might have had it fixed but I didn't read well enough.
My only concern is I would like to get Azure passing again ASAP. Should
I just grab that patch by itself then?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-01-12 20:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 0:14 [PATCH 1/4] ci: azure: Update to use stages Tom Rini
2022-01-12 0:14 ` [PATCH 2/4] CI, Dockerfile: Update to latest "focal" tag Tom Rini
2022-01-12 1:55 ` Fabio Estevam
2022-01-12 1:56 ` Tom Rini
2022-01-13 12:53 ` Tom Rini
2022-01-12 0:14 ` [PATCH 3/4] binman: Have faked binaries live in the output directory Tom Rini
2022-01-12 20:01 ` Simon Glass
2022-01-12 20:03 ` Tom Rini [this message]
2022-01-12 20:11 ` Simon Glass
2022-01-12 0:14 ` [PATCH 4/4] .readthedocs.yml: Set our requirements file Tom Rini
2022-01-12 2:33 ` Heinrich Schuchardt
2022-01-12 22:05 ` [PATCH 1/4] ci: azure: Update to use stages Tom Rini
2022-01-13 12:53 ` Tom Rini
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=20220112200311.GC9207@bill-the-cat \
--to=trini@konsulko.com \
--cc=heiko.thiery@gmail.com \
--cc=sjg@chromium.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox