From: Pavel Machek <pavel@denx.de>
To: Chris Paterson <chris.paterson2@renesas.com>,
cip-dev@lists.cip-project.org
Cc: Pavel Machek <pavel@denx.de>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"alice.ferrazzi@miraclelinux.com"
<alice.ferrazzi@miraclelinux.com>
Subject: Still random failures at gitlab
Date: Thu, 27 Oct 2022 21:24:40 +0200 [thread overview]
Message-ID: <20221027192440.GA11819@duo.ucw.cz> (raw)
In-Reply-To: <TYCPR01MB10588638D4BFDFF15F7CB9E98B7319@TYCPR01MB10588.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 6004 bytes --]
Hi!
I'm still getting random failures at gitlab. Is the info below enough
/ can I retry the tests now to get real results?
Thanks and best regards,
Pavel
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/679070235
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/3238998916
Running with gitlab-runner 15.4.0 (43b2dc3d)
2 on 1665142213-cip-project-small-v9-project-gitlab-runner-85dctt8xr Uf_MsYPS
3 feature flags: FF_KUBERNETES_HONOR_ENTRYPOINT:true
4
Resolving secrets
00:00
6
Preparing the "kubernetes" executor
00:00
7Using Kubernetes namespace: gitlab
8Using Kubernetes executor with image registry.gitlab.com/cip-project/cip-testing/linux-cip-ci:test-v3 ...
9Using attach strategy to execute scripts...
11
Preparing environment
03:07
12Waiting for pod gitlab/runner-ufmsyps-project-14394223-concurrent-0nzck6 to be running, status is Pending
13 Unschedulable: "0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling."
14Waiting for pod gitlab/runner-ufmsyps-project-14394223-concurrent-0nzck6 to be running, status is Pending
15 Unschedulable: "0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling."
16Waiting for pod gitlab/runner-ufmsyps-project-14394223-concurrent-0nzck6 to be running, status is Pending
17 Unschedulable: "0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling."
18Waiting for pod gitlab/runner-ufmsyps-project-14394223-concurrent-0nzck6 to be running, status is Pending
19 Unschedulable: "0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling."
20Waiting for pod gitlab/runner-ufmsyps-project-14394223-concurrent-0nzck6 to be running, status is Pending
21 Unschedulable: "0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling."
22Waiting for pod gitlab/runner-ufmsyps-project-14394223-concurrent-0nzck6 to be running, status is Pending
23 Unschedulable: "0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling."
24Waiting for pod gitlab/runner-ufmsyps-project-14394223-concurrent-0nzck6 to be running, status is Pending
25 Unschedulable: "0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling."
26Waiting for pod gitlab/runner-ufmsyps-project-14394223-concurrent-0nzck6 to be running, status is Pending
27 Unschedulable: "0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling."
28Waiting for pod gitlab/runner-ufmsyps-project-14394223-concurrent-0nzck6 to be running, status is Pending
29 Unschedulable: "0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling."
30Waiting for pod gitlab/runner-ufmsyps-project-14394223-concurrent-0nzck6 to be running, status is Pending
31 Unschedulable: "0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling."
32Waiting for pod gitlab/runner-ufmsyps-project-14394223-concurrent-0nzck6 to be running, status is Pending
33 Unschedulable: "0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling."
34Waiting for pod gitlab/runner-ufmsyps-project-14394223-concurrent-0nzck6 to be running, status is Pending
35 Unschedulable: "0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling."
36Waiting for pod gitlab/runner-ufmsyps-project-14394223-concurrent-0nzck6 to be running, status is Pending
37 Unschedulable: "0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling."
38Waiting for pod gitlab/runner-ufmsyps-project-14394223-concurrent-0nzck6 to be running, status is Pending
39 Unschedulable: "0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling."
40Waiting for pod gitlab/runner-ufmsyps-project-14394223-concurrent-0nzck6 to be running, status is Pending
41 Unschedulable: "0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling."
42Waiting for pod gitlab/runner-ufmsyps-project-14394223-concurrent-0nzck6 to be running, status is Pending
43 Unschedulable: "0/1 nodes are available: 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/1 nodes are available: 1 Preemption is not helpful for scheduling."
44Waiting for pod gitlab/runner-ufmsyps-project
--
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 --]
next prev parent reply other threads:[~2022-10-27 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 16:08 KernelCI, gitlab testing notes Pavel Machek
2022-10-21 8:05 ` [cip-dev] " Bezdeka, Florian
2022-10-25 15:57 ` Chris Paterson
2022-10-27 19:24 ` Pavel Machek [this message]
2022-10-27 19:26 ` Still random failures at gitlab Pavel Machek
2022-10-28 8:25 ` 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=20221027192440.GA11819@duo.ucw.cz \
--to=pavel@denx.de \
--cc=alice.ferrazzi@miraclelinux.com \
--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