From: "Zhou, JunX W" <junx.w.zhou@intel.com>
To: "Zhou, JunX W" <junx.w.zhou@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1] tests/TestSuite_short_live: Correct meson build omission error
Date: Wed, 4 Nov 2020 08:07:16 +0000 [thread overview]
Message-ID: <b5719281ef3546babfbc4b6b59fba569@intel.com> (raw)
In-Reply-To: <20201104080740.24143-1-junx.w.zhou@intel.com>
[-- Attachment #1: Type: text/plain, Size: 318 bytes --]
Tested-by: Zhou, Jun <junx.w.zhou@intel.com>
-----Original Message-----
From: Zhou Jun [mailto:junx.w.zhou@intel.com]
Sent: Wednesday, November 4, 2020 4:08 PM
To: dts@dpdk.org
Cc: Zhou, JunX W <junx.w.zhou@intel.com>
Subject: [dts][PATCH V1] tests/TestSuite_short_live: Correct meson build omission error
[-- Attachment #2: TestShortLiveApp.log --]
[-- Type: application/octet-stream, Size: 2843 bytes --]
04/11/2020 07:43:40 dts:
TEST SUITE : TestShortLiveApp
04/11/2020 07:43:40 dts: NIC : fortville_spirit
04/11/2020 07:43:40 dut.10.240.183.141:
04/11/2020 07:43:40 tester:
04/11/2020 07:43:40 TestShortLiveApp: Test Case test_start_up_time Begin
04/11/2020 07:43:40 dut.10.240.183.141:
04/11/2020 07:43:40 tester:
04/11/2020 07:43:40 dut.10.240.183.141: echo quit | time ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x3 -n 4 --no-pci -- -i
04/11/2020 07:43:40 dut.10.240.183.141: time: cannot run ./x86_64-native-linuxapp-gcc/app/testpmd: No such file or directory
Command exited with non-zero status 127
0.00user 0.00system 0:00.00elapsed 60%CPU (0avgtext+0avgdata 816maxresident)k
0inputs+0outputs (0major+24minor)pagefaults 0swaps
04/11/2020 07:44:34 TestShortLiveApp: Test Case test_start_up_time Result PASSED:
04/11/2020 07:44:34 dut.10.240.183.141: kill_all: called by dut and has no prefix list.
04/11/2020 07:44:34 dts:
TEST SUITE ENDED: TestShortLiveApp
04/11/2020 07:45:35 dts:
TEST SUITE : TestShortLiveApp
04/11/2020 07:45:35 dts: NIC : fortville_spirit
04/11/2020 07:45:36 dut.10.240.183.141:
04/11/2020 07:45:36 tester:
04/11/2020 07:45:36 TestShortLiveApp: Test Case test_start_up_time Begin
04/11/2020 07:45:36 dut.10.240.183.141:
04/11/2020 07:45:36 tester:
04/11/2020 07:45:36 dut.10.240.183.141: echo quit | time ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -c 0x3 -n 4 --no-pci -- -i
04/11/2020 07:45:37 dut.10.240.183.141: EAL: Detected 88 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: 1024 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: No legacy callbacks, legacy socket not created
testpmd: No probed ethernet devices
Interactive-mode selected
testpmd: create a new mbuf pool <mb_pool_0>: n=155456, size=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
Done
testpmd> quit
Bye...
0.11user 0.69system 0:00.81elapsed 99%CPU (0avgtext+0avgdata 59448maxresident)k
0inputs+0outputs (0major+10744minor)pagefaults 0swaps
04/11/2020 07:47:15 TestShortLiveApp: Test Case test_start_up_time Result PASSED:
04/11/2020 07:47:15 dut.10.240.183.141: kill_all: called by dut and has no prefix list.
04/11/2020 07:47:17 dts:
TEST SUITE ENDED: TestShortLiveApp
next prev parent reply other threads:[~2020-11-04 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 8:07 Zhou Jun
2020-11-04 8:07 ` Zhou, JunX W [this message]
2020-11-11 2:53 ` Tu, Lijuan
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=b5719281ef3546babfbc4b6b59fba569@intel.com \
--to=junx.w.zhou@intel.com \
--cc=dts@dpdk.org \
/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).