From: "Pavel Machek" <pavel@denx.de>
To: cip-dev@lists.cip-project.org
Cc: chris.paterson2@renesas.com
Subject: Re: [cip-dev] A lot of compiles failing
Date: Tue, 24 Nov 2020 19:44:58 +0100 [thread overview]
Message-ID: <20201124184458.GA7488@duo.ucw.cz> (raw)
In-Reply-To: <164A38B8F4B8DF4E.30699@lists.cip-project.org>
[-- Attachment #1.1: Type: text/plain, Size: 1508 bytes --]
Hi!
> This is going on for a few days now, but today it seems worse than
> usual:
>
> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/220169843
>
> builds are failing, 'HTTP 500 curl 22' error, so not a real build
> problem. I can probably just click restart... 6 times. But something
> is not there, and it is getting worse.
Today I got new one....
Waiting for pod gitlab/runner-bcrayztp-project-2678032-concurrent-392fb6 to be running, status is Pending
217Running on runner-bcrayztp-project-2678032-concurrent-392fb6 via cip-project-v3-gitlab-runner-6dbd79945f-wdqqw...
219
Fetching changes with git depth set to 10...
00:35
220Initialized empty Git repository in /builds/cip-project/cip-kernel/linux-cip/.git/
221Created fresh repository.
222error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: INTERNAL_ERROR (err 2)
223fatal: the remote end hung up unexpectedly
224fatal: early EOF
225fatal: index-pack failed
227
Uploading artifacts.
I wonder... Is each of our workers pulling full copy of kernel from
gitlab?
If so, I understand that gitlab might be a bit unhappy. We probably
should populate the initial version from our servers (or from
kernel.org), or maybe include copy of recent linux directly into
machine images... to reduce load on gitlab.
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: 420 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5861): https://lists.cip-project.org/g/cip-dev/message/5861
Mute This Topic: https://lists.cip-project.org/mt/78460850/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
next parent reply other threads:[~2020-11-24 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164A38B8F4B8DF4E.30699@lists.cip-project.org>
2020-11-24 18:44 ` Pavel Machek [this message]
2020-11-24 18:47 ` [cip-dev] A lot of compiles failing Sudip Mukherjee
2020-11-23 19:09 Pavel Machek
2020-12-01 9:52 ` Chris Paterson
2020-12-07 8:34 ` 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=20201124184458.GA7488@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;
as well as URLs for NNTP newsgroup(s).