From: Pavel Machek <pavel@denx.de>
To: Michael Adler <michael.adler@siemens.com>
Cc: Pavel Machek <pavel@denx.de>,
Chris Paterson <Chris.Paterson2@renesas.com>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"alice.ferrazzi@miraclelinux.com"
<alice.ferrazzi@miraclelinux.com>
Subject: Re: [cip-dev] gitlab test failures -- job failed ... pods not found
Date: Fri, 7 Oct 2022 12:15:29 +0200 [thread overview]
Message-ID: <20221007101529.GA25429@duo.ucw.cz> (raw)
In-Reply-To: <20221007065754.fysie7e4j2bvrvck@backstein>
[-- Attachment #1: Type: text/plain, Size: 770 bytes --]
Hi!
> > Still there, I'd say:
> >
> > https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/3123103311
>
> Ok, I have restored our previous cluster (v9). Please try again and tell me if the problem still persists. If it does,
> then I'd blame Gitlab I/O otherwise it could be a regression somewhere in the K8s stack - in that case, our best bet
> might be to sit it out.
It may be a bit better.
https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/660868595
Still see bbb failure, but that's different one:
https://lava.ciplatform.org/scheduler/job/756260
Thanks,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2022-10-07 10:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 10:50 gitlab test failures -- job failed ... pods not found Pavel Machek
2022-09-30 11:36 ` Chris Paterson
[not found] ` <1719A05389EC9CB2.16804@lists.cip-project.org>
2022-09-30 11:56 ` [cip-dev] " Chris Paterson
2022-10-04 7:53 ` Michael Adler
2022-10-06 11:50 ` Pavel Machek
2022-10-07 6:57 ` Michael Adler
2022-10-07 8:45 ` Chris Paterson
2022-10-07 9:27 ` Michael Adler
2022-10-07 9:38 ` Chris Paterson
[not found] ` <171BBFEDD39FD303.15379@lists.cip-project.org>
2022-10-07 10:01 ` Chris Paterson
2022-10-07 11:56 ` Michael Adler
2022-10-07 10:15 ` 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=20221007101529.GA25429@duo.ucw.cz \
--to=pavel@denx.de \
--cc=Chris.Paterson2@renesas.com \
--cc=alice.ferrazzi@miraclelinux.com \
--cc=cip-dev@lists.cip-project.org \
--cc=michael.adler@siemens.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.