From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: npg-prc-sw.stv@intel.com, waterman.cao@intel.com,
weichun.chen@archermind.com, npg-prc-sw.stv.cw@intel.com,
shijiex.dong@intel.com
Subject: [dpdk-test-report] [ERROR]DPDK Regression Test Report
Date: 23 Feb 2016 16:19:20 -0800 [thread overview]
Message-ID: <acb6cf$rfonms@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2875 bytes --]
Summary:
============================================================================================================================================
| DPDK commit | e277b239708a86b4ec17f8df468e76ab764f8f3f
--------------------------------------------------------------------------------------------------------------------------------------------
| Author | Thomas Monjalon <thomas.monjalon@6wind.com>
--------------------------------------------------------------------------------------------------------------------------------------------
| Date | Thu Feb 18 201632 2016 +0100
--------------------------------------------------------------------------------------------------------------------------------------------
| Comment | aesni_mb: fix build clean
============================================================================================================================================
+------------+----------------------+------------+--------------------------------+--------+-------------------------------------+--------+
| OS | NIC | TestType | Kernel | GCC | Target | Result |
| | | | | | | (F/T) |
+============+======================+============+================================+========+=====================================+========+
| UB1510 | Niantic | Smoke | 4.2.0-16-generic | 5.2.1 | x86_64-native-linuxapp-gcc | 0/91 |
+------------+----------------------+------------+--------------------------------+--------+-------------------------------------+--------+
| SuSe12 | Niantic | Smoke | 3.12.28-4-default | 4.8.3 | x86_64-native-linuxapp-gcc | 1/91 |
+------------+----------------------+------------+--------------------------------+--------+-------------------------------------+--------+
Total:2
Failed Case List:
+----------------------+-------------------------------------+-----------------------------------------------+
| Platform | Target | Failed cases |
+======================+=====================================+===============================================+
| UB1510_Niantic_Smoke | x86_64-native-linuxapp-gcc | N/A |
+----------------------+-------------------------------------+-----------------------------------------------+
| SuSe12_Niantic_Smoke | x86_64-native-linuxapp-gcc | jumboframes_jumbo_jumbo |
+----------------------+-------------------------------------+-----------------------------------------------+
next reply other threads:[~2016-02-24 0:19 UTC|newest]
Thread overview: 95+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 0:19 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-25 0:10 sys_stv
2016-10-24 0:03 sys_stv
2016-10-23 0:10 sys_stv
2016-10-22 0:01 sys_stv
2016-10-21 0:03 sys_stv
2016-10-20 0:01 sys_stv
2016-10-19 0:14 sys_stv
2016-10-18 0:01 sys_stv
2016-10-17 0:16 sys_stv
2016-10-16 0:05 sys_stv
2016-10-15 0:01 sys_stv
2016-10-14 0:01 sys_stv
2016-10-11 0:01 sys_stv
2016-09-30 0:01 sys_stv
2016-09-28 0:03 sys_stv
2016-09-22 0:01 sys_stv
2016-09-21 0:01 sys_stv
2016-09-20 0:01 sys_stv
2016-09-19 0:05 sys_stv
2016-09-18 0:14 sys_stv
2016-09-17 0:09 sys_stv
2016-09-16 0:09 sys_stv
2016-09-15 0:05 sys_stv
2016-09-14 0:07 sys_stv
2016-09-13 0:07 sys_stv
2016-09-12 0:07 sys_stv
2016-09-11 0:01 sys_stv
2016-09-10 0:05 sys_stv
2016-09-09 0:01 sys_stv
2016-06-06 23:56 sys_stv
2016-06-05 23:59 sys_stv
2016-06-04 23:56 sys_stv
2016-06-03 23:56 sys_stv
2016-06-02 23:58 sys_stv
2016-06-01 23:59 sys_stv
2016-05-24 23:57 sys_stv
2016-05-12 23:58 sys_stv
2016-05-11 23:57 sys_stv
2016-05-08 23:59 sys_stv
2016-05-07 23:58 sys_stv
2016-05-06 23:57 sys_stv
2016-05-05 23:58 sys_stv
2016-04-28 23:59 sys_stv
2016-04-27 23:59 sys_stv
2016-04-25 23:59 sys_stv
2016-04-21 23:57 sys_stv
2016-04-20 23:59 sys_stv
2016-04-18 23:57 sys_stv
2016-04-16 23:57 sys_stv
2016-04-15 23:59 sys_stv
2016-04-14 23:59 sys_stv
2016-04-13 23:58 sys_stv
2016-04-11 23:59 sys_stv
2016-04-10 23:58 sys_stv
2016-04-09 23:58 sys_stv
2016-04-08 23:59 sys_stv
2016-04-07 23:59 sys_stv
2016-04-07 0:00 sys_stv
2016-04-05 23:57 sys_stv
2016-04-05 8:04 sys_stv
2016-04-05 1:18 sys_stv
2016-03-26 2:28 sys_stv
2016-03-25 2:24 sys_stv
2016-03-24 0:00 sys_stv
2016-03-23 0:28 sys_stv
2016-03-22 2:30 sys_stv
2016-03-18 3:31 sys_stv
2016-03-17 3:43 sys_stv
2016-03-15 23:59 sys_stv
2016-03-15 1:59 sys_stv
2016-03-14 7:24 sys_stv
2016-03-13 4:04 sys_stv
2016-03-12 4:04 sys_stv
2016-03-11 3:41 sys_stv
2016-03-07 23:58 sys_stv
2016-03-06 23:58 sys_stv
2016-03-06 0:00 sys_stv
2016-03-04 0:00 sys_stv
2016-03-03 0:00 sys_stv
2016-02-29 1:25 sys_stv
2016-02-20 0:37 sys_stv
2016-02-19 0:36 sys_stv
2016-02-18 0:34 sys_stv
2016-02-17 0:22 sys_stv
2016-02-16 1:28 sys_stv
2016-02-05 1:41 sys_stv
2016-02-02 23:59 sys_stv
2016-01-31 23:59 sys_stv
2016-01-31 0:00 sys_stv
2016-01-29 23:59 sys_stv
2016-01-28 23:59 sys_stv
2016-01-28 0:00 sys_stv
2016-01-26 23:59 sys_stv
2016-01-21 23:59 sys_stv
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='acb6cf$rfonms@fmsmga002.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=npg-prc-sw.stv.cw@intel.com \
--cc=npg-prc-sw.stv@intel.com \
--cc=shijiex.dong@intel.com \
--cc=test-report@dpdk.org \
--cc=waterman.cao@intel.com \
--cc=weichun.chen@archermind.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).