From: qabuild@intel.com
To: waterman.cao@intel.com, haifengx.tang@intel.com,
thomas.monjalon@6wind.com, dpdk_sw_eng@intel.com,
limin.wang@intel.com, xiaopengx.zhang@intel.com,
junchunx.guan@intel.com, test-report@dpdk.org
Subject: [dpdk-test-report] [build-report] DPDK OS Building Test Report
Date: Tue, 12 Jan 2016 12:05:52 +0800 [thread overview]
Message-ID: <f6d642$qem82@fmsmga004.fm.intel.com> (raw)
[-- Attachment #1: report.html --]
[-- Type: text/html, Size: 20728 bytes --]
[-- Attachment #2: build_logs.zip --]
[-- Type: x-gzip, Size: 168991 bytes --]
next reply other threads:[~2016-01-12 4:05 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 4:05 qabuild [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-01-12 2:33 qabuild
2016-01-06 23:05 qabuild
2016-01-05 23:08 qabuild
2016-01-05 4:19 qabuild
2016-01-02 23:03 qabuild
2016-01-01 23:05 qabuild
2015-12-31 23:07 qabuild
2015-12-30 23:05 qabuild
2015-12-29 23:05 qabuild
2015-12-28 23:05 qabuild
2015-12-27 23:05 qabuild
2015-12-26 23:05 qabuild
2015-12-25 23:09 qabuild
2015-12-24 23:05 qabuild
2015-12-23 23:07 qabuild
2015-12-22 23:05 qabuild
2015-12-21 23:06 qabuild
2015-12-20 23:05 qabuild
2015-12-19 23:05 qabuild
2015-12-18 23:09 qabuild
2015-12-17 23:05 qabuild
2015-12-16 23:05 qabuild
2015-12-15 23:05 qabuild
2015-12-14 23:05 qabuild
2015-12-14 4:51 qabuild
2015-12-13 23:03 qabuild
2015-12-12 23:03 qabuild
2015-12-11 23:05 qabuild
2015-12-10 22:48 qabuild
2015-12-09 23:05 qabuild
2015-12-09 9:10 qabuild
2015-12-09 3:37 qabuild
2015-12-08 6:47 qabuild
2015-12-07 23:01 qabuild
2015-12-07 7:27 qabuild
2015-12-07 4:35 qabuild
2015-12-06 23:13 qabuild
2015-12-05 23:07 qabuild
2015-12-04 23:09 qabuild
2015-12-03 23:07 qabuild
2015-12-02 23:07 qabuild
2015-12-01 23:11 qabuild
2015-11-30 23:07 qabuild
2015-11-30 1:34 qabuild
2015-11-29 1:58 qabuild
2015-11-28 1:28 qabuild
2015-11-26 23:04 qabuild
2015-11-26 2:35 qabuild
2015-11-25 23:07 qabuild
2015-11-24 23:04 qabuild
2015-11-23 23:02 qabuild
2015-11-22 23:02 qabuild
2015-11-21 23:02 qabuild
2015-11-20 23:02 qabuild
2015-11-19 22:51 qabuild
2015-11-18 22:51 qabuild
2015-11-17 22:51 qabuild
2015-11-16 22:50 qabuild
2015-11-15 22:51 qabuild
2015-11-14 22:50 qabuild
2015-11-13 22:50 qabuild
2015-11-12 22:48 qabuild
2015-11-11 22:21 qabuild
2015-11-10 22:21 qabuild
2015-11-10 6:21 qabuild
2015-11-10 2:41 qabuild
2015-11-09 22:23 qabuild
2015-11-03 22:24 qabuild
2015-11-02 22:22 qabuild
2015-11-02 2:35 qabuild
2015-11-02 2:19 qabuild
2015-10-30 1:44 qabuild
2015-10-18 22:49 qabuild
2015-10-17 22:49 qabuild
2015-10-16 22:49 qabuild
2015-10-16 9:39 qabuild
2015-10-16 8:00 qabuild
2015-10-16 7:36 qabuild
2015-10-16 6:55 qabuild
2015-10-16 6:50 qabuild
2015-10-15 22:49 qabuild
2015-10-14 22:49 qabuild
2015-10-13 22:49 qabuild
2015-10-12 22:49 qabuild
2015-10-11 22:49 qabuild
2015-10-10 22:49 qabuild
2015-10-10 7:42 qabuild
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='f6d642$qem82@fmsmga004.fm.intel.com' \
--to=qabuild@intel.com \
--cc=dpdk_sw_eng@intel.com \
--cc=haifengx.tang@intel.com \
--cc=junchunx.guan@intel.com \
--cc=limin.wang@intel.com \
--cc=test-report@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=waterman.cao@intel.com \
--cc=xiaopengx.zhang@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).