All of lore.kernel.org
 help / color / mirror / Atom feed
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] gitlab problems: -stable mirring broken, testing broken?
Date: Fri, 9 Apr 2021 14:48:28 +0000	[thread overview]
Message-ID: <OSAPR01MB23856AC5EA12705FF23A62C5B7739@OSAPR01MB2385.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20210409112257.GA13478@amd>

[-- Attachment #1: Type: text/plain, Size: 1521 bytes --]

Hello Pavel,

> From: Pavel Machek <pavel@denx.de>
> Sent: 09 April 2021 12:23
>
> Hi!
>
> gitlab seems to have some problems. 5.10.29-rc1 is not mirrored in
> gitlab:
>
> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-
> 5.10.y

It looks like the webhook from https://gitlab.com/cip-project/cip-testing/linux-stable-rc didn't get through.
I've tried again and hit a 429 error:
"Hook executed successfully but returned HTTP 429 Rate limit exceeded; see https://docs.gitlab.com/ee/user/gitlab_com/#gitlabcom-specific-rate-limits for more details"

Maybe we've hit one of these rate limits?

>
> And I'm getting strange error while attempting to test 4.4 kernel:
>
> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/283833338
>
> Found errors in your .gitlab-ci.yml:
> Remote file
> `https://gitlab.com/cip-project/cip-testing/linux-cip-
> pipelines/raw/master/linux-cip-pipeline.yml`
> could not be fetched because of HTTP code `429` error!
> You can also test your .gitlab-ci.yml in CI Lint

It looks like the same issue as above.
I've kicked off a pipeline for the same branch and it's working now:
https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/284020976

Kind regards, Chris


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

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


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6356): https://lists.cip-project.org/g/cip-dev/message/6356
Mute This Topic: https://lists.cip-project.org/mt/81965841/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/4520388/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-


      reply	other threads:[~2021-04-09 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 11:22 [cip-dev] gitlab problems: -stable mirring broken, testing broken? Pavel Machek
2021-04-09 14:48 ` Chris Paterson [this message]

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=OSAPR01MB23856AC5EA12705FF23A62C5B7739@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.