cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: "Chris Paterson" <chris.paterson2@renesas.com>
To: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
	"cip-members@lists.cip-project.org"
	<cip-members@lists.cip-project.org>
Subject: Re: [cip-dev] CIP LAVA maintenance
Date: Fri, 19 Mar 2021 07:06:04 +0000	[thread overview]
Message-ID: <OSBPR01MB2392E14F337E62A92502D5B1B7689@OSBPR01MB2392.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <166D61BDF351CC05.5206@lists.cip-project.org>

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

Hello all,

> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On
> Behalf Of Chris Paterson via lists.cip-project.org
> Sent: 18 March 2021 08:15
> 
> Hello all,
> 
> 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.

Kind regards, Chris

> 
> I'll keep you updated.
> 
> Kind regards, Chris

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


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


       reply	other threads:[~2021-03-19  7:06 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 ` Chris Paterson [this message]
2021-03-19 11:24   ` [cip-dev] CIP LAVA maintenance Pavel Machek
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=OSBPR01MB2392E14F337E62A92502D5B1B7689@OSBPR01MB2392.jpnprd01.prod.outlook.com \
    --to=chris.paterson2@renesas.com \
    --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 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).