public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Chris Paterson <Chris.Paterson2@renesas.com>
Cc: Pavel Machek <pavel@denx.de>,
	"nobuhiro1.iwamatsu@toshiba.co.jp"
	<nobuhiro1.iwamatsu@toshiba.co.jp>,
	"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
	"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>,
	"uli@fpond.eu" <uli@fpond.eu>,
	"masami.ichikawa@cybertrust.co.jp"
	<masami.ichikawa@cybertrust.co.jp>,
	"van Buuren Sietze (XC-CT/EMT2)" <Sietze.vanBuuren@de.bosch.com>
Subject: squad was Re: [ANNOUNCE] Release and and v6.1.78-cip15
Date: Fri, 1 Mar 2024 12:41:20 +0100	[thread overview]
Message-ID: <ZeG+4IMAEEcc0lPy@duo.ucw.cz> (raw)
In-Reply-To: <TYWPR01MB11862BFA542FA685652E73FA8B75A2@TYWPR01MB11862.jpnprd01.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]

Hi!

> > . Is that expected? How should we deal with those?
> 
> 
> 
> If the "incomplete" LAVA job has a green ticket next to it (as in this case), the job has already been resubmitted and successfully run again.
> 
> If there is a red cross, a LAVA job failed to complete and hasn't been resubmitted yet.
> 
> SQUAD admins (me & Sietze) can resubmit these LAVA jobs directly from SQUAD, then SQUAD automatically keeps track of it all.
>

Still looking at Squad. I submitted test merge to LAVA, and it is now
being tested at

https://gitlab.com/cip-project/cip-kernel/linux-cip/tree/ci/pavel/linux-test

. Where can I find it in SQUAD?

And while browsing around, I stepped on this:

https://squad.ciplatform.org/linux-cip/

There is still lot of skips and fails there. The 5.10 ones are from 9
hours ago. What is going on there?

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2024-03-01 11:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-25 23:26 [ANNOUNCE] Release and and v6.1.78-cip15 nobuhiro1.iwamatsu
2024-02-26 10:06 ` Chris Paterson
2024-02-26 12:05   ` Pavel Machek
2024-02-26 12:18     ` Chris Paterson
2024-03-01 11:41       ` Pavel Machek [this message]

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=ZeG+4IMAEEcc0lPy@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=Chris.Paterson2@renesas.com \
    --cc=Sietze.vanBuuren@de.bosch.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.kiszka@siemens.com \
    --cc=masami.ichikawa@cybertrust.co.jp \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    --cc=uli@fpond.eu \
    /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