From: "Pavel Machek" <pavel@denx.de>
To: cip-dev@lists.cip-project.org
Cc: "cip-members@lists.cip-project.org" <cip-members@lists.cip-project.org>
Subject: Re: [cip-dev] CIP LAVA maintenance
Date: Fri, 19 Mar 2021 12:24:59 +0100 [thread overview]
Message-ID: <20210319112459.GA27349@amd> (raw)
In-Reply-To: <OSBPR01MB2392E14F337E62A92502D5B1B7689@OSBPR01MB2392.jpnprd01.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 2105 bytes --]
Hi!
> > The CIP LAVA infrastructure will be going down for maintenance very soon.
> > Upgrade Gods permitting, it will all be back online later today.
>
> Sorry for the delayed notice. All of the labs are back online now.
Thank you, Renesas boards appear to work.
But I still see random failures from
test:x86_siemens_ipc227e_defconfig :
Pipeline #273166880 has failed!
Project: linux-cip (
https://gitlab.com/cip-project/cip-kernel/linux-cip )
Branch: ci/pavel/linux-test (
+https://gitlab.com/cip-project/cip-kernel/linux-cip/-/commits/ci/pavel/linux-test
)
Commit: a58c985b (
+https://gitlab.com/cip-project/cip-kernel/linux-cip/-/commit/a58c985b03f0b798625dc2890bb8b
+cf17caf5995 )
Commit Message: arm64: dts: renesas: Add support for MIPI Adapt...
Commit Author: Lad Prabhakar
Committed by: Pavel Machek
Pipeline #273166880 (
+https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/273166880
) triggered by
+Pavel Machek ( https://gitlab.com/pavelm )
had 1 failed build.
Job #1111610478 (
https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/1111610478/raw
+)
Stage: test
Name: test:x86_siemens_ipc227e_defconfig
Simple resubmit fixed it:
Pipeline has been fixed and #273166880 has passed!
Project: linux-cip (
https://gitlab.com/cip-project/cip-kernel/linux-cip )
Branch: ci/pavel/linux-test (
+https://gitlab.com/cip-project/cip-kernel/linux-cip/-/commits/ci/pavel/linux-test
)
Commit: a58c985b (
+https://gitlab.com/cip-project/cip-kernel/linux-cip/-/commit/a58c985b03f0b798625dc2890bb8b
+cf17caf5995 )
Commit Message: arm64: dts: renesas: Add support for MIPI Adapt...
Commit Author: Lad Prabhakar
Committed by: Pavel Machek
Pipeline #273166880 (
+https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/273166880
) triggered by
+Pavel Machek ( https://gitlab.com/pavelm )
successfully completed 23 jobs in 2 stages.
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 (#6303): https://lists.cip-project.org/g/cip-dev/message/6303
Mute This Topic: https://lists.cip-project.org/mt/81424532/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 prev parent reply other threads:[~2021-03-19 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166D61BDF351CC05.5206@lists.cip-project.org>
2021-03-19 7:06 ` [cip-dev] CIP LAVA maintenance Chris Paterson
2021-03-19 11:24 ` Pavel Machek [this message]
2021-03-22 5:58 ` Nobuhiro Iwamatsu
2021-03-18 8:15 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=20210319112459.GA27349@amd \
--to=pavel@denx.de \
--cc=cip-dev@lists.cip-project.org \
--cc=cip-members@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 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.