Re: [PATCH 3/4] binman: Have faked binaries live in the output directory.

Simon Glass
2022-01-12T20:11:39Z

Hi Tom,

On Wed, 12 Jan 2022 at 13:03, Tom Rini <trini@konsulko.com> wrote:
>
> 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?

Yes, but I just sent v2 rebased to master (two patches).

Regards,
Simon