From: Tom Rini <trini@konsulko.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Leonard Anderweit <L.Anderweit@phytec.de>,
"sjg@chromium.org" <sjg@chromium.org>,
"brian.ruley@gehealthcare.com" <brian.ruley@gehealthcare.com>,
"marex@denx.de" <marex@denx.de>,
"ravi@prevas.dk" <ravi@prevas.dk>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
"paul.henrys_ext@softathome.com" <paul.henrys_ext@softathome.com>,
"tharvey@gateworks.com" <tharvey@gateworks.com>
Subject: Re: [PATCH] binman: Fill in most of the imx8mimage and imx8mcst tests
Date: Mon, 31 Mar 2025 12:31:18 -0600 [thread overview]
Message-ID: <20250331183118.GL93000@bill-the-cat> (raw)
In-Reply-To: <CAOMZO5BtELcioQPygHGx6rsRmFvxeStn-PFf3B22BeXkgUbepw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 561 bytes --]
On Mon, Mar 31, 2025 at 03:18:12PM -0300, Fabio Estevam wrote:
> Hi Leonard,
>
> On Mon, Mar 31, 2025 at 11:43 AM Leonard Anderweit
> <L.Anderweit@phytec.de> wrote:
>
> > The error looks like binman is never building the missing tools.
> > Run something like:
> > ./tools/binman/binman tool -f missing
> > before the binman tests.
> >
> > This test setup uses .gitlab-ci.yml, right?
>
> Yes, I think so.
>
> Care to submit a patch that fixes this CI problem?
And make similar changes to .azure-pipelines.yml as well please.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-03-31 18:31 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-05 20:36 [PATCH] binman: Fill in most of the imx8mimage and imx8mcst tests Marek Vasut
2025-01-06 14:38 ` Simon Glass
2025-01-06 20:50 ` Marek Vasut
2025-01-07 3:50 ` Simon Glass
2025-01-07 10:39 ` Marek Vasut
2025-01-09 14:10 ` Simon Glass
2025-01-10 11:02 ` Fabio Estevam
2025-02-05 10:19 ` Marek Vasut
2025-02-06 12:42 ` Simon Glass
2025-02-06 20:40 ` Marek Vasut
2025-02-07 0:49 ` Simon Glass
2025-02-08 21:19 ` Marek Vasut
2025-02-15 13:38 ` Simon Glass
2025-02-15 14:55 ` Marek Vasut
2025-03-06 23:30 ` Simon Glass
2025-03-07 0:04 ` Marek Vasut
2025-03-07 2:18 ` Simon Glass
2025-03-07 5:42 ` Marek Vasut
2025-03-12 0:41 ` Fabio Estevam
2025-03-19 23:54 ` Marek Vasut
2025-03-20 3:40 ` Simon Glass
2025-03-20 4:05 ` Marek Vasut
2025-03-28 11:42 ` Simon Glass
2025-03-28 13:23 ` Fabio Estevam
2025-03-31 14:43 ` Leonard Anderweit
2025-03-31 18:18 ` Fabio Estevam
2025-03-31 18:31 ` Tom Rini [this message]
2025-05-05 12:28 ` Fabio Estevam
2025-05-05 14:46 ` Tom Rini
2025-03-30 22:11 ` Marek Vasut
2025-03-31 1:18 ` 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=20250331183118.GL93000@bill-the-cat \
--to=trini@konsulko.com \
--cc=L.Anderweit@phytec.de \
--cc=brian.ruley@gehealthcare.com \
--cc=festevam@gmail.com \
--cc=marex@denx.de \
--cc=paul.henrys_ext@softathome.com \
--cc=ravi@prevas.dk \
--cc=sjg@chromium.org \
--cc=tharvey@gateworks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox