automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: weichunx.chen@intel.com, haifengx.tang@intel.com,
	yufengx.mo@intel.com, yong.liu@intel.com, test-report@dpdk.org,
	qian.q.xu@intel.com, waterman.cao@intel.com,
	shide.dong@intel.com
Subject: [dpdk-test-report] |ERROR| pw 7703 eal: refactor plugin list append from eal_parse_args() to a helper function
Date: 16 Oct 2015 06:19:57 -0700	[thread overview]
Message-ID: <e9ea37$ols1jf@orsmga002.jf.intel.com> (raw)

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

Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork: http://www.dpdk.org/dev/patchwork/patch/7703/

DPDK git baseline: affc455438f4cbd3b14e2d9a24fbc154e22d68d3
Patchwork ID: 7703
http://www.dpdk.org/dev/patchwork/patch/7703/
Submitter: Panu Matilainen <pmatilai@redhat.com>
Date: Fri, 16 Oct 2015 14:58:13 +0300

Compilation:
OS: fedora
Nic: niantic
i686-native-linuxapp-gcc: compile pass
x86_64-native-linuxapp-gcc: compile pass

DTS validation: 
OS: fedora
Nic: Niantic
TestType: auto
GCC: 4
x86_64-native-linuxapp-gcc:  total 75, passed 74, failed 1.
Failed Case List:
Target: x86_64-native-linuxapp-gcc
OS: fedora
Failed DTS case: 
checksum_checking: http://dpdk.org/browse/tools/dts/tree/test_plans/pmd_test_plan.rst

DTS Validation Error:
========================================================================================================================
========================================================================================================================
TEST SUITE : TestPmd

-------------------------------------------------------------------------------
Begin: Test Casetest_checksum_checking
--------------------------------------------------
FAILED  'packet pass assert error, expected 60 RX bytes, actual 0'
--------------------------------------------------
[   SUITE_DUT_CMD]  ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x1fffffffff -n 4  -- -i --coremask=0x2 --portmask=0x3 --nb-cores=2 --enable-rx-cksum --disable-hw-vlan --disable-rss --crc-strip --rxd=1024 --txd=1024 --rxfreet=0 --txqflags=0
[   SUITE_DUT_CMD]  set fwd csum
[   SUITE_DUT_CMD]  start
[   SUITE_DUT_CMD]  show port stats 0
[   SUITE_DUT_CMD]  show port stats 1
[SUITE_TESTER_CMD]  echo -n '' >  scapyResult.txt
[SUITE_TESTER_CMD]  killall scapy 2>/dev/null; echo tester
[SUITE_TESTER_CMD]  scapy
[SUITE_TESTER_CMD]  nutmac="90:e2:ba:4a:54:81"
[SUITE_TESTER_CMD]  sendp([Ether(dst=nutmac, src="52:00:00:00:00:00")/IP(len=46)/UDP(chksum=0x0)/Raw(load="P"*18)], iface="p785p2")
[SUITE_TESTER_CMD]  exit()
[   SUITE_DUT_CMD]  show port stats 0
[   SUITE_DUT_CMD]  show port stats 1
End test_checksum_checking
-------------------------------------------------------------------------------
[SUITE_TESTER_CMD] killall scapy 2>/dev/null; echo tester



DPDK STV team 

                 reply	other threads:[~2015-10-16 13:20 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='e9ea37$ols1jf@orsmga002.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=haifengx.tang@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=shide.dong@intel.com \
    --cc=test-report@dpdk.org \
    --cc=waterman.cao@intel.com \
    --cc=weichunx.chen@intel.com \
    --cc=yong.liu@intel.com \
    --cc=yufengx.mo@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).