From: "Pavel Machek" <pavel@denx.de>
To: cip-dev@lists.cip-project.org, chris.paterson2@renesas.com
Subject: [cip-dev] gitlab problems: -stable mirring broken, testing broken?
Date: Fri, 9 Apr 2021 13:22:57 +0200 [thread overview]
Message-ID: <20210409112257.GA13478@amd> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 754 bytes --]
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
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
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: 428 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#6355): https://lists.cip-project.org/g/cip-dev/message/6355
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]
-=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~2021-04-09 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 11:22 Pavel Machek [this message]
2021-04-09 14:48 ` [cip-dev] gitlab problems: -stable mirring broken, testing broken? 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=20210409112257.GA13478@amd \
--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).