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 7373-7375 example: PTP client slave minimal implementation
Date: 02 Oct 2015 10:14:15 -0700 [thread overview]
Message-ID: <2d8c1b$nt4snr@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2632 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: ERROR
Patchwork: http://www.dpdk.org/dev/patchwork/patch/7375/
DPDK git baseline: affc455438f4cbd3b14e2d9a24fbc154e22d68d3
Patchwork ID: 7373-7375
http://www.dpdk.org/dev/patchwork/patch/7375/
Submitter: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
Date: Fri, 2 Oct 2015 17:20:08 +0200
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:
ieee1588_enable: http://dpdk.org/browse/tools/dts/tree/test_plans/ieee1588_test_plan.rst
DTS Validation Error:
========================================================================================================================
========================================================================================================================
TEST SUITE : TestIeee1588
[SUITE_DUT_CMD] sed -i -e 's/IEEE1588=n$/IEEE1588=y/' config/common_linuxapp
[SUITE_DUT_CMD] rm -rf x86_64-native-linuxapp-gcc
[SUITE_DUT_CMD] make -j install T=x86_64-native-linuxapp-gcc
[SUITE_DUT_CMD] ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x6 -n 4 -- -i --txqflags=0
-------------------------------------------------------------------------------
Begin: Test Casetest_ieee1588_enable
--------------------------------------------------
FAILED 'Timestamp mismatch'
--------------------------------------------------
[ SUITE_DUT_CMD] set fwd ieee1588
[ SUITE_DUT_CMD] start
[SUITE_TESTER_CMD] echo -n '' > scapyResult.txt
[SUITE_TESTER_CMD] scp sniff.py root@10.239.128.80:~/
[SUITE_TESTER_CMD] SCAPY Receive setup:
[SUITE_TESTER_CMD] killall scapy 2>/dev/null; echo tester
[SUITE_TESTER_CMD] scapy
[SUITE_TESTER_CMD] subprocess.call("scapy -c sniff.py &", shell=True)
[SUITE_TESTER_CMD] nutmac="90:e2:ba:4a:54:80"
[SUITE_TESTER_CMD] sendp([Ether(dst=nutmac,type=0x88f7)/"\x00\x02"], iface="p785p1")
[SUITE_TESTER_CMD] time.sleep(1)
[SUITE_TESTER_CMD] exit()
[SUITE_TESTER_CMD] cat scapyResult.txt
[SUITE_TESTER_CMD] SCAPY Result:
[ SUITE_DUT_CMD] stop
End test_ieee1588_enable
-------------------------------------------------------------------------------
[ SUITE_DUT_CMD] quit
[ SUITE_DUT_CMD] sed -i -e 's/IEEE1588=y$/IEEE1588=n/' config/common_linuxapp
[ SUITE_DUT_CMD] rm -rf x86_64-native-linuxapp-gcc
[ SUITE_DUT_CMD] make -j install T=x86_64-native-linuxapp-gcc
[SUITE_TESTER_CMD] killall scapy 2>/dev/null; echo tester
DPDK STV team
reply other threads:[~2015-10-02 17:14 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='2d8c1b$nt4snr@fmsmga001.fm.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).