From: Tom Rini <trini@konsulko.com>
To: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
Cc: Andrejs Cainikovs <andrejs.cainikovs@toradex.com>,
Simon Glass <sjg@chromium.org>,
U-Boot Mailing List <u-boot@lists.denx.de>,
Leo Yu-Chi Liang <ycliang@andestech.com>,
Marek Vasut <marek.vasut+renesas@mailbox.org>
Subject: Re: [PATCH v3 19/19] CI: Allow running tests on sjg lab
Date: Mon, 24 Jun 2024 12:01:49 -0600 [thread overview]
Message-ID: <20240624180149.GF38804@bill-the-cat> (raw)
In-Reply-To: <CAOf5uwkQDzOpj-XUojvfWD6tU2cOxZkv4OEvOK7eZJZcRHTjfg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]
On Mon, Jun 24, 2024 at 04:56:02PM +0200, Michael Nazzareno Trimarchi wrote:
> Hi Simon
>
> On Mon, Jun 24, 2024 at 2:52 PM Andrejs Cainikovs
> <andrejs.cainikovs@toradex.com> wrote:
> >
> > On Sun, Jun 23, 2024 at 02:32:13PM -0600, Simon Glass wrote:
> > > Add a way to run tests on a real hardware lab. This is in the very early
> > > experimental stages. There are only 23 boards and 3 of those are broken!
> > > (bob, ff3399, samus). A fourth fails due to problems with the TPM tests.
> > >
> > > To try this, assuming you have gitlab access, set SJG_LAB=1, e.g.:
> > >
> > > git push -o ci.variable="SJG_LAB=1" dm HEAD:try
> > >
> > > This relies on the two previous series targeted at -next as well as the
> > > bugfix series for -master
> > >
> > > Signed-off-by: Simon Glass <sjg@chromium.org>
> >
> > Reviewed-by: Andrejs Cainikovs <andrejs.cainikovs@toradex.com>
> >
>
> Do you have documentation on how to set it? We would like to do in our
> company too
I _think_ from some talking with Simon before the biggest sticking point
might be changes needed on the labgrid side of things. However, that
might also be most easily remedied if there's a few people showing up in
the GitHub issue(s) showing interest in getting changes made/merged and
to use the overall feature.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-06-24 18:01 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 20:31 [PATCH v3 00/19] labgrid: Provide an integration with Labgrid Simon Glass
2024-06-23 20:31 ` [PATCH v3 01/19] test: Allow signaling that U-Boot is ready Simon Glass
2024-06-23 20:31 ` [PATCH v3 02/19] test: Use a constant for the test timeout Simon Glass
2024-06-23 20:31 ` [PATCH v3 03/19] test: Pass stderr to stdout Simon Glass
2024-06-23 20:31 ` [PATCH v3 04/19] test: Release board after tests complete Simon Glass
2024-06-23 20:31 ` [PATCH v3 05/19] test: Allow connecting to a running board Simon Glass
2024-06-23 20:32 ` [PATCH v3 06/19] test: Avoid failing skipped tests Simon Glass
2024-06-24 18:05 ` Tom Rini
2024-06-25 12:38 ` Simon Glass
2024-06-25 14:14 ` Tom Rini
2024-06-26 8:00 ` Simon Glass
2024-06-26 13:56 ` Tom Rini
2024-06-26 13:59 ` Tom Rini
2024-08-22 3:00 ` Simon Glass
2024-08-22 14:11 ` Tom Rini
2024-08-22 14:22 ` Simon Glass
2024-08-22 14:29 ` Tom Rini
2024-06-23 20:32 ` [PATCH v3 07/19] test: Create a common function to get the config Simon Glass
2024-06-23 20:32 ` [PATCH v3 08/19] test: Introduce the concept of a role Simon Glass
2024-06-24 18:13 ` Tom Rini
2024-06-25 12:38 ` Simon Glass
2024-06-25 14:27 ` Tom Rini
2024-06-26 8:00 ` Simon Glass
2024-06-26 14:29 ` Tom Rini
2024-06-27 8:37 ` Simon Glass
2024-07-02 23:12 ` Tom Rini
2024-07-13 15:13 ` Simon Glass
2024-07-13 16:57 ` Tom Rini
2024-07-15 7:11 ` Simon Glass
2024-07-15 21:03 ` Tom Rini
2024-07-31 14:39 ` Simon Glass
2024-06-23 20:32 ` [PATCH v3 09/19] test: Move the receive code into a function Simon Glass
2024-06-23 20:32 ` [PATCH v3 10/19] test: Separate out the exception handling Simon Glass
2024-06-23 20:32 ` [PATCH v3 11/19] test: Detect dead connections Simon Glass
2024-06-23 20:32 ` [PATCH v3 12/19] test: Tidy up remaining exceptions Simon Glass
2024-06-23 20:32 ` [PATCH v3 13/19] test: Introduce lab mode Simon Glass
2024-06-23 20:32 ` [PATCH v3 14/19] test: Improve handling of sending commands Simon Glass
2024-06-23 20:32 ` [PATCH v3 15/19] test: Fix mulptiplex_log typo Simon Glass
2024-06-23 20:32 ` [PATCH v3 16/19] test: Avoid double echo when starting up Simon Glass
2024-06-23 20:32 ` [PATCH v3 17/19] test: Try to shut down the lab console gracefully Simon Glass
2024-06-23 20:32 ` [PATCH v3 18/19] test: Add a section for closing the connection Simon Glass
2024-06-23 20:32 ` [PATCH v3 19/19] CI: Allow running tests on sjg lab Simon Glass
2024-06-24 7:13 ` Andrejs Cainikovs
2024-06-24 14:56 ` Michael Nazzareno Trimarchi
2024-06-24 18:01 ` Tom Rini [this message]
2024-06-25 12:30 ` Simon Glass
2024-08-09 16:10 ` 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=20240624180149.GF38804@bill-the-cat \
--to=trini@konsulko.com \
--cc=andrejs.cainikovs@toradex.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=michael@amarulasolutions.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=ycliang@andestech.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.