public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: "Pavel Machek" <pavel@denx.de>
To: cip-dev@lists.cip-project.org
Cc: Pavel Machek <pavel@denx.de>
Subject: Re: [cip-dev] A lot of compiles failing
Date: Mon, 7 Dec 2020 09:34:59 +0100	[thread overview]
Message-ID: <20201207083459.GA26656@amd> (raw)
In-Reply-To: <OSAPR01MB23853004B735A607C4BEE0C5B7F40@OSAPR01MB2385.jpnprd01.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 1164 bytes --]

Hi!

> > 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?

I still see them:

https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/225881953

2 builds failed, for example:

https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/893211490

225
Cloning into '.'...
00:32
226$ git clone --depth 10 --branch $CI_COMMIT_REF_NAME
https://gitlab.com/cip-project/cip-testing/linux-stable-rc.git .
227error: RPC failed; HTTP 500 curl 22 The requested URL returned
error: 500 Server Error
228fatal: The remote end hung up unexpectedly

Best regards,
								Pavel

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5946): https://lists.cip-project.org/g/cip-dev/message/5946
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]
-=-=-=-=-=-=-=-=-=-=-=-


  reply	other threads:[~2020-12-07  8:35 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
2020-12-07  8:34   ` Pavel Machek [this message]
     [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=20201207083459.GA26656@amd \
    --to=pavel@denx.de \
    --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