All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>,
	Alper Nebi Yasak <alpernebiyasak@gmail.com>
Subject: binman and faked blobs failures
Date: Mon, 11 Apr 2022 17:28:30 -0400	[thread overview]
Message-ID: <20220411212830.GC14282@bill-the-cat> (raw)

[-- Attachment #1: Type: text/plain, Size: 2391 bytes --]

Hey,

So here's a problem I have.  Today if I'm in a branch that has a commit
that's not in it's upstream branch (so lets say I'm testing a bunch of
patches I grabbed from patchwork in a local branch that knows master is
the upstream) and I do:

export SOURCE_DATE_EPOCH=1649712313
./tools/buildman/buildman -o /tmp/chromebook_samus -devl --step 0 -b testing -SBC chromebook_samus
Building 2 commits for 2 boards (2 threads, 8 jobs per thread)
01: linux/mtd/mtd.h: Add <dm/ofnode.h>
       x86:  w+   chromebook_samus
+(chromebook_samus) Image 'main-section' is missing external blobs and is non-functional: intel-descriptor intel-me intel-refcode intel-vga intel-mrc
+(chromebook_samus) Image 'main-section' has faked external blobs and is non-functional: descriptor.bin me.bin refcode.bin vga.bin mrc.bin
+(chromebook_samus)
+(chromebook_samus) Some images are invalid
02: HACK
       x86:  +   chromebook_samus
+(chromebook_samus) binman: Node '/binman/rom/intel-descriptor': Cannot find Intel Flash Descriptor (FD) signature
+(chromebook_samus) make[1]: *** [Makefile:1101: all] Error 1
+(chromebook_samus) make: *** [Makefile:177: sub-make] Error 2
01: linux/mtd/mtd.h: Add <dm/ofnode.h>
       x86:  w+   chromebook_samus_tpl
+(chromebook_samus_tpl) Image 'main-section' is missing external blobs and is non-functional: intel-descriptor intel-me intel-refcode intel-vga intel-mrc
+(chromebook_samus_tpl) Image 'main-section' has faked external blobs and is non-functional: descriptor.bin me.bin refcode.bin vga.bin mrc.bin
+(chromebook_samus_tpl)
+(chromebook_samus_tpl) Some images are invalid
02: HACK
       x86:  +   chromebook_samus_tpl
+(chromebook_samus_tpl) binman: Node '/binman/rom/intel-descriptor': Cannot find Intel Flash Descriptor (FD) signature
+(chromebook_samus_tpl) make[1]: *** [Makefile:1101: all] Error 1
+(chromebook_samus_tpl) make: *** [Makefile:177: sub-make] Error 2
    0    2    2 /4              chromebook_samus_tpl
Completed: 4 total built, duration 0:00:31, rate 0.13

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.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

             reply	other threads:[~2022-04-11 21:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 21:28 Tom Rini [this message]
2022-04-16 17:30 ` binman and faked blobs failures Alper Nebi Yasak
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=20220411212830.GC14282@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=alpernebiyasak@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 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.