From: Pavel Machek <pavel@nabladev.com>
To: cip-dev@lists.cip-project.org, Chris.Paterson2@renesas.com
Subject: No boards available for testing -- everything failing on gitlab
Date: Mon, 2 Mar 2026 11:02:33 +0100 [thread overview]
Message-ID: <aaVgOTtbrrgEHL2A@duo.ucw.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
Hi!
I see all the runtime tests failing on gitlab (compilations work ok)
-- 0 boards available.
https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/2357934585
57
09:56:19
There are currently 0 "r9a07g043f01-smarc-rzfive" devices online.
58
09:56:19
Refusing to submit test job as there are no suitable devices
available.
...
(And similar for other boards).
Can someone take a look?
Thanks,
Pavel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next reply other threads:[~2026-03-02 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 10:02 Pavel Machek [this message]
2026-03-02 10:16 ` No boards available for testing -- everything failing on gitlab Chris Paterson
[not found] ` <1898FECF736AF5EE.1454197@lists.cip-project.org>
2026-03-03 12:14 ` [cip-members] " Chris Paterson
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=aaVgOTtbrrgEHL2A@duo.ucw.cz \
--to=pavel@nabladev.com \
--cc=Chris.Paterson2@renesas.com \
--cc=cip-dev@lists.cip-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