From: Kuan-Wei Chiu <visitorckw@gmail.com>
To: trini@konsulko.com
Cc: tuomas.tynkkynen@iki.fi, bmeng.cn@gmail.com, sjg@chromium.org,
jerome.forissier@arm.com, jserv@ccns.ncku.edu.tw,
eleanor15x@gmail.com, marscheng@google.com,
u-boot@lists.u-boot-project.org,
Kuan-Wei Chiu <visitorckw@gmail.com>
Subject: [PATCH] Azure: Switch u-boot-test-hooks to git.u-boot-project.org
Date: Wed, 7 Oct 2026 20:42:34 +0000 [thread overview]
Message-ID: <20261007204234.1081107-1-visitorckw@gmail.com> (raw)
Azure pipelines still clones u-boot-test-hooks from the github mirror,
which is missing the recent qemu arm64 9P device setup and causes the
9P test to fail to find a 9P device. Switch it to
git.u-boot-project.org like gitlab CI.
Signed-off-by: Kuan-Wei Chiu <visitorckw@gmail.com>
---
.azure-pipelines.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.azure-pipelines.yml b/.azure-pipelines.yml
index 5bda11a0309..d88dc35dea1 100644
--- a/.azure-pipelines.yml
+++ b/.azure-pipelines.yml
@@ -279,7 +279,7 @@ stages:
# the below corresponds to .gitlab-ci.yml "before_script"
cd \${WORK_DIR}
git config --global --add safe.directory \${WORK_DIR}
- git clone --depth=1 https://github.com/u-boot/u-boot-test-hooks /tmp/uboot-test-hooks
+ git clone --depth=1 https://git.u-boot-project.org/u-boot/u-boot-test-hooks /tmp/uboot-test-hooks
# qemu_arm64_lwip_defconfig is the same as qemu_arm64 but with NET_LWIP enabled.
# The test config and the boardenv file from qemu_arm64 can be re-used so create symlinks
ln -s conf.qemu_arm64 /tmp/uboot-test-hooks/bin/travis-ci/conf.qemu_arm64_lwip_na
--
2.56.0.360.g66cac248cb-goog
next reply other threads:[~2026-10-07 22:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 20:42 Kuan-Wei Chiu [this message]
2026-10-07 20:55 ` [PATCH] Azure: Switch u-boot-test-hooks to git.u-boot-project.org Kuan-Wei Chiu
2026-10-08 1:09 ` Bin Meng
2026-10-08 1:36 ` Tom Rini
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=20261007204234.1081107-1-visitorckw@gmail.com \
--to=visitorckw@gmail.com \
--cc=bmeng.cn@gmail.com \
--cc=eleanor15x@gmail.com \
--cc=jerome.forissier@arm.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=marscheng@google.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=tuomas.tynkkynen@iki.fi \
--cc=u-boot@lists.u-boot-project.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