From: sys_stv@intel.com
To: weichunx.chen@intel.com, haifengx.tang@intel.com,
yufengx.mo@intel.com, yong.liu@intel.com,
thomas.monjalon@6wind.com, dts@dpdk.org, qian.q.xu@intel.com,
waterman.cao@intel.com, shide.dong@intel.com
Subject: [dts] |ERROR|pw 6973 [dpdk-dev, v3, 1/1] ip_frag: fix creating ipv6 fragment extension header
Date: 09 Sep 2015 07:23:28 -0700 [thread overview]
Message-ID: <f90827$mq1jp0@orsmga001.jf.intel.com> (raw)
Summary:
=====================================================================================================================================================================================
| DPDK git baseline | 17e01e3141aa520042eb1fa705b3472757350bab
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| Patchwork ID | 6973 | http://www.dpdk.org/dev/patchwork/patch/6973/
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| Submitter | Piotr Azarewicz <piotrx.t.azarewicz@intel.com>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| Date | Wed, 9 Sep 2015 15:39:05 +0200
=====================================================================================================================================================================================
| OS | Nic |
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| fedora | niantic |
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| i686-native-linuxapp-gcc | compile pass
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| x86_64-native-linuxapp-gcc | compile pass
=====================================================================================================================================================================================
| Failed case | Test Plan
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| kni | http://dpdk.org/browse/tools/dts/tree/test_plans/unit_tests_kni_test_plan.rst
=====================================================================================================================================================================================
| DTS validation
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| OS | Nic | TestType | Kernel | GCC | Target | Result(F/T)
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| fedora | Niantic | auto | | 4 | x86_64-native-linuxapp-gcc| total 76, pass 75, failed 1
=====================================================================================================================================================================================
Failed Case List:
========================================================================================================================================
\ | | | |
\Target| | | |
\ | x86_64-native-linuxapp-gcc | i686-native-linuxapp-gcc | x86_64-native-bsdapp-gcc |
OS \ | | | |
\| | | |
----------------------------------------------------------------------------------------------------------------------------------------
fedora | | N/A | N/A |
|kni | | |
========================================================================================================================================
| DTS Validation Error |
========================================================================================================================
========================================================================================================================
TEST SUITE : TestUnitTestsKni
[SUITE_DUT_CMD] make -C ./app/test/
[SUITE_DUT_CMD] lsmod | grep rte_kni
[SUITE_DUT_CMD] insmod ./x86_64-native-linuxapp-gcc/kmod/rte_kni.ko lo_mode=lo_mode_fifo
-------------------------------------------------------------------------------
Begin: Test Casetest_kni
--------------------------------------------------
FAILED 'Test Failed'
--------------------------------------------------
[SUITE_DUT_CMD] ./app/test/test -n 1 -c fffe
[SUITE_DUT_CMD] kni_autotest
[SUITE_DUT_CMD] quit
End test_kni
-------------------------------------------------------------------------------
[ SUITE_DUT_CMD] rmmod rte_kni
[SUITE_TESTER_CMD] killall scapy 2>/dev/null; echo tester
DPDK STV team
reply other threads:[~2015-09-09 14:23 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='f90827$mq1jp0@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=dts@dpdk.org \
--cc=haifengx.tang@intel.com \
--cc=qian.q.xu@intel.com \
--cc=shide.dong@intel.com \
--cc=thomas.monjalon@6wind.com \
--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).