From: "Chris Paterson" <chris.paterson2@renesas.com>
To: Pavel Machek <pavel@denx.de>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] A lot of compiles failing
Date: Tue, 1 Dec 2020 09:52:31 +0000 [thread overview]
Message-ID: <OSAPR01MB23853004B735A607C4BEE0C5B7F40@OSAPR01MB2385.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20201123190940.GA13627@duo.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 1701 bytes --]
Hello Pavel,
> From: Pavel Machek <pavel@denx.de>
> Sent: 23 November 2020 19:10
>
> *** gpg4o | The signature of this email could not be verified because the
> following public key is missing. Click here to search and import the key
> 30E7F06A95DBFAF2 ***
>
> Hi!
>
> This is going on for a few days now, but today it seems worse than
> usual:
For me things seems to have stabilised now.
Are you still seeing a lot of issues?
Kind regards, Chris
>
> 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.
>
> Best regards,
> Pavel
>
>
> g for pod gitlab/runner-bcrayztp-project-2678032-concurrent-7hmhsr to be
> running, status is Pending
> 74Running on runner-bcrayztp-project-2678032-concurrent-7hmhsr via cip-
> project-v3-gitlab-runner-6dbd79945f-wdqqw...
> 76
> Fetching changes with git depth set to 10...
> 00:18
> 77Initialized empty Git repository in /builds/cip-project/cip-kernel/linux-
> cip/.git/
> 78Created fresh repository.
> 79error: RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
> 80fatal: the remote end hung up unexpectedly
> 82
> Uploading artifacts...
> 00:00
> 83WARNING: output: no matching files
> 84ERROR: No files to upload
> 86ERROR: Job failed: command terminated with exit code 1
> --
> DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: Type: text/plain, Size: 420 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5928): https://lists.cip-project.org/g/cip-dev/message/5928
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 prev parent reply other threads:[~2020-12-01 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 19:09 [cip-dev] A lot of compiles failing Pavel Machek
2020-12-01 9:52 ` Chris Paterson [this message]
2020-12-07 8:34 ` Pavel Machek
[not found] <164A38B8F4B8DF4E.30699@lists.cip-project.org>
2020-11-24 18:44 ` Pavel Machek
2020-11-24 18:47 ` Sudip Mukherjee
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=OSAPR01MB23853004B735A607C4BEE0C5B7F40@OSAPR01MB2385.jpnprd01.prod.outlook.com \
--to=chris.paterson2@renesas.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;
as well as URLs for NNTP newsgroup(s).