DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: dpdk-dev <dev@dpdk.org>
Subject: RE: Expect slowness in CI during the week of Feb 5
Date: Mon, 30 Jan 2023 10:39:42 +0000	[thread overview]
Message-ID: <BYAPR12MB30784CACAA5C6A90438A71D7CFD39@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <BYAPR12MB3078468D102B2BA035FDFA47CFD39@BYAPR12MB3078.namprd12.prod.outlook.com>

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

You can disregard this email! It was sent by mistake to the wrong mailing address.
Sorry for the spam!

Kindest regards,
Raslan Darawsheh

From: Raslan Darawsheh
Sent: Monday, January 30, 2023 12:34 PM
To: dpdk-team <dpdk-team@exchange.nvidia.com>; dpdk-dev <dev@dpdk.org>; shys-org <shys-org@exchange.nvidia.com>
Cc: Ali Alnubani <alialnu@nvidia.com>; Shy Shyman <shys@nvidia.com>
Subject: Expect slowness in CI during the week of Feb 5
Importance: High

Hi Guys,

Because we are migrating our servers from MTR to MTL,
We need to have a shutdown for some of our services/servers in MTR which will affect our CI.

In general, the services should continue working, but with a slower resolution time.
One of our services (dpdk-tests) will be fully down (can’t be running per PR) during this time.
For that, we need your help to make sure you are running the cloud regression yourself on each PR you have. (follow this guideline<https://confluence.nvidia.com/display/NSWX/How+to+run+DPDK+regression+on+cloud+setups>)


Kindest regards,
Raslan Darawsheh


[-- Attachment #2: Type: text/html, Size: 4694 bytes --]

      reply	other threads:[~2023-01-30 10:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30 10:33 Raslan Darawsheh
2023-01-30 10:39 ` Raslan Darawsheh [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=BYAPR12MB30784CACAA5C6A90438A71D7CFD39@BYAPR12MB3078.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.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).