From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "ci@dpdk.org" <ci@dpdk.org>,
"test-report@dpdk.org" <test-report@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"O'Driscoll, Tim" <tim.odriscoll@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-ci] build system have been recovered
Date: Fri, 21 Sep 2018 09:45:01 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20EED0597@SHSMSX151.ccr.corp.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 597 bytes --]
Hi,
Everything is back in order.
Thanks
Lijuan
From: Tu, Lijuan
Sent: Friday, September 21, 2018 9:40 AM
To: ci@dpdk.org; 'test-report@dpdk.org' <test-report@dpdk.org>; Yigit, Ferruh <ferruh.yigit@intel.com>; O'Driscoll, Tim <tim.odriscoll@intel.com>; 'Thomas Monjalon' <thomas@monjalon.net>
Subject: build system will be offline for several days due to lab migration
Hi,
Intel lab is being migrated, and this will block DPDK CI , so per patch set build and daily build will be offline for several days.
We will recover it ASAP, sorry for any inconvenience.
Thanks
Lijuan
[-- Attachment #2: Type: text/html, Size: 4294 bytes --]
reply other threads:[~2018-09-21 9:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8CE3E05A3F976642AAB0F4675D0AD20EED0597@SHSMSX151.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=ci@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
--cc=tim.odriscoll@intel.com \
/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).