From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |SUCCESS| pw(76916) [RFC] app/testpmd: distinguish ICMP identifier fields in packet
Date: 09 Sep 2020 18:01:03 -0700 [thread overview]
Message-ID: <fecc85$b8gp1k@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3205 bytes --]
Test-Label: Intel-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/76916
_Compilation OK_
Submitter: lizh <lizh@nvidia.com>
Date: 2020-09-08 10:06:36
Reply_mail: 20200908100636.4575-1-lizh@nvidia.com
DPDK git baseline: Repo:dpdk-next-net, CommitID: 592fd96ea8ab8ec5ec6a345cb6f8fb6e87bb953a
Meson build Summary: 8 Builds Done, 8 Successful, 0 Failures, 0 Blocked
+===========+==========+
| Meson | Document |
+----------------+-----------+----------+
| os | gcc/clang | pdf/html |
+----------------+-----------+----------+
| CENTOS82-64 | pass | |
| UB2004-64 | pass | pass |
| FC32-64 | pass | |
| WIN10-64 | pass | |
| UB2004-32 | pass | |
| FreeBSD1201-64 | pass | |
| SUSE15-64 | pass | |
+----------------+-----------+----------+
Test environment and configuration as below:
** Meson build **
OS: CENTOS82-64
Kernel Version: 4.18.0-193.el8.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (GCC) 8.3.1 20191121 (Red Hat 8.3.1-5)
Clang Version: 9.0.1 (Red Hat 9.0.1-2.module_el8.2.0+309+0c7b6b03)
./build-gcc-static
./build-gcc-shared
./build-clang-static
./build-clang-shared
./build-x86-default
OS: UB2004-64
Kernel Version: 5.4.0-26-generic
CPU info: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
GCC Version: gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0
Clang Version: 10.0.0-4ubuntu1
x86_64-native-linuxapp-doc
./build-gcc-static
./build-gcc-shared
./build-clang-static
./build-clang-shared
./build-x86-default
OS: FC32-64
Kernel Version: 5.6.0-0.rc7.git0.2.fc32.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (GCC) 10.0.1 20200311 (Red Hat 10.0.1-0.9)
Clang Version: 10.0.0 (Fedora 10.0.0-0.3.rc4.fc32)
./build-gcc-static
./build-gcc-shared
./build-clang-static
./build-clang-shared
./build-x86-default
OS: WIN10-64
Kernel Version: N/A
CPU info: N/A
GCC Version: N/A
Clang Version: Clang 8.0.0
x86_64-windows-clang
OS: UB2004-32
Kernel Version: 5.4.0-26-generic
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0
Clang Version: 10.0.0-4ubuntu1
./build-gcc-static
./build-gcc-shared
./build-x86-default
/root/UB2004-32_K4.15.0_GCC9.3.0/i686-native-linuxapp-gcc/5be2ddcc0e5f4ed6967f765916240bfc/dpdk/build-x86-default install >/dev/null
OS: FreeBSD1201-64
Kernel Version: 12.1-RELEASE
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz (2194.97-MHz K8-class CPU)
GCC Version: gcc (FreeBSD Ports Collection) 9.2.0
Clang Version: 8.0.1 (tags/RELEASE_801/final 366581) (based on LLVM 8.0.1)
./build-gcc-static
./build-gcc-shared
./build-clang-static
./build-clang-shared
./build-x86-default
OS: SUSE15-64
Kernel Version: 4.12.14-lp150.12.82-default
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (SUSE Linux) 7.4.1 20190905 [gcc-7-branch revision 275407]
Clang Version: 5.0.1 (tags/RELEASE_501/final 312548)
./build-gcc-static
./build-gcc-shared
./build-clang-static
./build-clang-shared
./build-x86-default
DPDK STV team
reply other threads:[~2020-09-10 1:01 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='fecc85$b8gp1k@orsmga001.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=test-report@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).