From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 3/6] ci: container: update to newer Labgrid
Date: Mon, 12 Aug 2024 11:15:19 +0200 [thread overview]
Message-ID: <20240812091522.3035469-3-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20240812091522.3035469-1-a.fatoum@pengutronix.de>
The now current release is v23.0.6 from April 2024, but master has
fixes, which enable us to run Labgrid tests against the sandbox
architecture. Therefore point at the newest commit on the master branch.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
test/Containerfile | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/test/Containerfile b/test/Containerfile
index 2f8c969d824f..c09051a1505a 100644
--- a/test/Containerfile
+++ b/test/Containerfile
@@ -75,8 +75,9 @@ RUN echo barebox ALL=NOPASSWD: ALL > /etc/sudoers.d/barebox
# install labgrid
RUN cd /tmp && \
- git clone --depth 1 -b v23.0 https://github.com/labgrid-project/labgrid && \
+ git clone --depth 1 https://github.com/labgrid-project/labgrid && \
cd labgrid && \
+ git checkout 16db15a953 && \
pip3 install --break-system-packages . && \
ln -s $(which pytest) /usr/local/bin/labgrid-pytest;
--
2.39.2
next prev parent reply other threads:[~2024-08-12 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 9:15 [PATCH 1/6] ci: container: update to Debian Bookworm with GCC v14.2.0 Ahmad Fatoum
2024-08-12 9:15 ` [PATCH 2/6] ci: container: add kvx-elf- toolchain Ahmad Fatoum
2024-08-12 9:29 ` Yann Sionneau
2024-08-12 9:15 ` Ahmad Fatoum [this message]
2024-08-12 12:52 ` [PATCH 3/6] ci: container: update to newer Labgrid Yann Sionneau
2024-08-12 13:30 ` Ahmad Fatoum
2024-08-12 9:15 ` [PATCH 4/6] test: sandbox: support testing with Labgrid Ahmad Fatoum
2024-08-12 9:15 ` [PATCH 5/6] ci: pytest: test sandbox configuration with labgrid Ahmad Fatoum
2024-08-12 9:15 ` [PATCH 6/6] ci: build: add kvx build test Ahmad Fatoum
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=20240812091522.3035469-3-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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