From: Michael Adler <michael.adler@siemens.com>
To: Pavel Machek <pavel@denx.de>
Cc: 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 08:57:54 +0200 [thread overview]
Message-ID: <20221007065754.fysie7e4j2bvrvck@backstein> (raw)
In-Reply-To: <20221006115033.GB21855@duo.ucw.cz>
> 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.
Kind Regards,
Michael
--
Michael Adler
Siemens AG
T CED SES-DE
Otto-Hahn-Ring 6
81739 München, Deutschland
Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Jim Hagemann Snabe; Vorstand: Roland Busch, Vorsitzender; Klaus Helmrich, Cedrik Neike, Matthias Rebellius, Ralf P. Thomas, Judith Wiese; Sitz der Gesellschaft: Berlin und München, Deutschland; Registergericht: Berlin-Charlottenburg, HRB 12300, München, HRB 6684; WEEE-Reg.-Nr. DE 23691322
next prev parent reply other threads:[~2022-10-07 6:58 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 [this message]
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
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=20221007065754.fysie7e4j2bvrvck@backstein \
--to=michael.adler@siemens.com \
--cc=Chris.Paterson2@renesas.com \
--cc=alice.ferrazzi@miraclelinux.com \
--cc=cip-dev@lists.cip-project.org \
--cc=pavel@denx.de \
/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