cip-dev.lists.cip-project.org archive mirror
 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] Testing of -stable-rc fails completely
Date: Tue, 29 Dec 2020 21:27:08 +0000	[thread overview]
Message-ID: <OSAPR01MB23857C22D82B59C59F0AD25BB7D80@OSAPR01MB2385.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20201229085357.GA17217@amd>

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

Hi Pavel,

> From: Pavel Machek <pavel@denx.de>
> Sent: 29 December 2020 08:54
>
> *** 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!
>
> It seems -stable-rc tests are now failing completely in "cloning
> repository" phase:
>
> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-
> /jobs/934209886
>
> Skipping Git submodules setup
> 99
> $ echo "Cloning linux-stable-rc" # collapsed multi-line command
> 00:30
> 100Cloning linux-stable-rc
> 101fatal: repository '.' does not exist
> 102fatal: repository '.' does not exist
> 103fatal: repository '.' does not exist
> 106
> Uploading artifacts...
> 00:00
> 107WARNING: output: no matching files
>
> Any ideas?

Thank you for reporting.
I had a typo in my latest change to the CI pipeline ?
I've fixed this now and the latest builds are going through now.

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: 420 bytes --]


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5980): https://lists.cip-project.org/g/cip-dev/message/5980
Mute This Topic: https://lists.cip-project.org/mt/79287435/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-29 21:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29  8:53 [cip-dev] Testing of -stable-rc fails completely Pavel Machek
2020-12-29 21:27 ` Chris Paterson [this message]
2020-12-30 12:45   ` Starting testing of 5.10-stable? was " Pavel Machek
2021-01-04 10:48     ` Chris Paterson
2021-01-04 12:15       ` 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=OSAPR01MB23857C22D82B59C59F0AD25BB7D80@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).