automatic DPDK test reports
 help / color / mirror / Atom feed
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] [Regression][PASSED]DPDK Regression Test Report
Date: 07 Jan 2016 22:53:12 -0800	[thread overview]
Message-ID: <2d8c1b$q4fbg7@fmsmga001.fm.intel.com> (raw)

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


Summary:

============================================================================================================================================
|  DPDK commit   |     3b60ce8cbb959d7a6839f94ad995a3594c07801e
--------------------------------------------------------------------------------------------------------------------------------------------
|     Author     |     John McNamara <john.mcnamara@intel.com>
--------------------------------------------------------------------------------------------------------------------------------------------
|      Date      |      Wed Dec 16 104250 2015 +0000
--------------------------------------------------------------------------------------------------------------------------------------------
|    Comment     |      doc: fix missing link target in Linux guide
============================================================================================================================================
|     OS    |           Nic            |    TestType   |             Kernel            |   GCC   |           Target          | Result(F/T) 
--------------------------------------------------------------------------------------------------------------------------------------------
|  Fedora22 | Fortville_spirit_single  |   Functional  |     4.0.4-301.fc22.x86_64     |  5.1.1  | x86_64-native-linuxapp-gcc|    0/107    
============================================================================================================================================


Failed Case List:

======================================================================================
                  \                        |                                         |
                   \Target                 |                                         |
                    \                      |        x86_64-native-linuxapp-gcc       |
                  OS \                     |                                         |
                      \                    |                                         |
-------------------------------------------------------------------------------------
Fedora22_Fortville_spirit_single_Functional|                                         |
                                           |                   N/A                   |
======================================================================================


DPDK STV team 

             reply	other threads:[~2016-01-08  6:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08  6:53 sys_stv [this message]
2016-01-11  2:11 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='2d8c1b$q4fbg7@fmsmga001.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).