From: Tom Rini <trini@konsulko.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: "marex@denx.de" <marex@denx.de>,
"sjg@chromium.org" <sjg@chromium.org>,
"brian.ruley@gehealthcare.com" <brian.ruley@gehealthcare.com>,
"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>,
Leonard Anderweit <l.anderweit@phytec.de>
Subject: Re: [PATCH] binman: Fill in most of the imx8mimage and imx8mcst tests
Date: Mon, 5 May 2025 08:46:24 -0600 [thread overview]
Message-ID: <20250505144624.GC5430@bill-the-cat> (raw)
In-Reply-To: <CAOMZO5ARjb5g4q6xATR8snQ8OJQnQBWfPQsUqUFEX=62=F3-pw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 585 bytes --]
On Mon, May 05, 2025 at 09:28:19AM -0300, Fabio Estevam wrote:
> Hi Marek and Tom,
>
> On Mon, Mar 31, 2025 at 3:31 PM Tom Rini <trini@konsulko.com> wrote:
>
> > And make similar changes to .azure-pipelines.yml as well please.
>
> I made another attempt and still get CI errors when applying this
> patch. zstd is not found in CI:
The Dockerfile needs to install zstd then it seems. You can't install it
like binman is trying to do, in CI at least, because there's no apt
archive cache (it's not included in the container, as a normal best
practice).
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2025-05-05 14:46 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
2025-05-05 12:28 ` Fabio Estevam
2025-05-05 14:46 ` Tom Rini [this message]
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=20250505144624.GC5430@bill-the-cat \
--to=trini@konsulko.com \
--cc=brian.ruley@gehealthcare.com \
--cc=festevam@gmail.com \
--cc=l.anderweit@phytec.de \
--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