From: "Pavel Machek" <pavel@denx.de>
To: Chris Paterson <Chris.Paterson2@renesas.com>
Cc: Pavel Machek <pavel@denx.de>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] -stable-rc tests failing
Date: Fri, 13 Aug 2021 21:46:35 +0200 [thread overview]
Message-ID: <20210813194635.GB23237@duo.ucw.cz> (raw)
In-Reply-To: <OSZPR01MB68775BA605A2B969F3B22612B7F89@OSZPR01MB6877.jpnprd01.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 1444 bytes --]
Hi!
> > WARNING: Retrying... error=invalid argument
> > 2170ERROR: Downloading artifacts from coordinator... error couldn't execute
> > GET against https://gitlab.com/api/v4/jobs/1492901612/artifacts?: Get
> > https://gitlab.com/api/v4/jobs/1492901612/artifacts?: dial tcp: i/o timeout
> > id=1492901612 token=9gNGsuaZ
> > 2171FATAL: invalid argument
> > 2173
> > Uploading artifacts for failed job
> >
> > But I don't usually see this one:
> >
> > https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-
> > /jobs/1492901660
> >
> > Job #371616: Submitted
> > 219Health: Unknown
> > 220Device Type: r8a7743-iwg20d-q7
> > 221Device: None
> > 222Test: boot
> > 223URL: https://lava.ciplatform.org/scheduler/job/371616
> > 224
> > 226ERROR: Job failed: execution took longer than 2h0m0s seconds
>
> It looks like the LAVA server has stopped processing jobs. Our queue has become very large!
> I'll have to see what died and no doubt reboot it and the labs.
>
> Sorry for the pain.
Thank you, it seems to be better now, and it looks like ctj_zynqmp is
available, too (I have not yet seen successful test, but it at least
tries).
But I still see problems with x86_qemu... the "2h timeout".
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 429 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6678): https://lists.cip-project.org/g/cip-dev/message/6678
Mute This Topic: https://lists.cip-project.org/mt/84811238/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/10495289/4520388/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2021-08-13 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 6:39 [cip-dev] -stable-rc tests failing Pavel Machek
2021-08-11 8:03 ` Chris Paterson
2021-08-13 19:46 ` Pavel Machek [this message]
2021-08-15 23:15 ` Nobuhiro Iwamatsu
2021-08-16 20:39 ` Chris Paterson
[not found] ` <169BE3F8982B564E.22901@lists.cip-project.org>
2021-08-16 20:58 ` Chris Paterson
2021-08-16 22:50 ` Nobuhiro Iwamatsu
-- strict thread matches above, loose matches on Subject: below --
2021-04-05 14:41 Pavel Machek
2021-04-06 7:48 ` 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=20210813194635.GB23237@duo.ucw.cz \
--to=pavel@denx.de \
--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