From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw(86197) [v8, 4/4] examples/ifpga: add example for opae ifpga API
Date: 11 Jan 2021 00:01:36 -0800 [thread overview]
Message-ID: <93cfb9$h0rld3@fmsmga005-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5684 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/86197
_Compilation issues_
Submitter: Wei Huang <wei.huang@intel.com>
Date: 2021-01-08 09:33:24
Reply_mail: 1610098404-3687-5-git-send-email-wei.huang@intel.com
DPDK git baseline: Repo:dpdk-next-net-intel, CommitID: b227f1aa6c5dd5f1d07f041956f645a14f04d794
Meson Build Summary: 22 Builds Done, 21 Successful, 1 Failures, 0 Blocked
+------------------+------------+--------------+------------+------------+-----------+----------+
| os | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document |
+------------------+------------+--------------+------------+------------+-----------+----------+
| UB2004-64 | pass | pass | pass | | | FAIL |
| RHEL83-64 | pass | | | | | |
| FC33-64 | pass | pass | | | | |
| CentOsStream8-64 | pass | | | | | |
| UB2010-64 | pass | | | | | |
| WIN10-64 | | pass | | | | |
| UB2004-32 | pass | | | | | |
| CENTOS83-64 | pass | pass | pass | pass | pass | |
| FreeBSD1201-64 | pass | pass | | pass | pass | |
| SUSE15-64 | pass | pass | | | | |
+------------------+------------+--------------+------------+------------+-----------+----------+
Test environment and configuration as below:
OS: UB2004-64
Kernel Version: 5.6.0-050600-generic
CPU info: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
GCC Version: gcc (Ubuntu 10-20200416-0ubuntu1) 10.0.1 20200416 (experimental) [master revision 3c3f12e2a76:dcee354ce56:44b326839d864fc10c459916abcc97f35a9ac3de]
Clang Version: 10.0.0-4ubuntu1
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-icc
x86_64-native-linuxapp-doc
OS: RHEL83-64
Kernel Version: 4.18.0-240.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: 10.0.1 (Red Hat 10.0.1-1.module+el8.3.0+7459+90c24896)
x86_64-native-linuxapp-gcc
OS: FC33-64
Kernel Version: 5.8.16-300.fc33.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (GCC) 10.2.1 20201005 (Red Hat 10.2.1-5)
Clang Version: 11.0.0 (Fedora 11.0.0-1.fc33)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
OS: CentOsStream8-64
Kernel Version: 4.18.0-257.el8.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (GCC) 8.4.1 20200928 (Red Hat 8.4.1-1)
Clang Version: 11.0.0 (Red Hat 11.0.0-0.2.rc2.module_el8.4.0+533+50191577)
x86_64-native-linuxapp-gcc
OS: UB2010-64
Kernel Version: 5.8.0-25-generic
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0
Clang Version: 11.0.0-2
x86_64-native-linuxapp-gcc
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.6.0-050600-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
i686-native-linuxapp-gcc
OS: CENTOS83-64
Kernel Version: 4.18.0-240.1.1.el8_3.x86_64
CPU info: Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
GCC Version: gcc (GCC) 8.3.1 20191121 (Red Hat 8.3.1-5)
Clang Version: 10.0.1 (Red Hat 10.0.1-1.module_el8.3.0+467+cb298d5b)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-icc
x86_64-native-linuxapp-gcc+shared
x86_64-native-linuxapp-gcc+debug
OS: FreeBSD1201-64
Kernel Version: 12.1-RELEASE
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz (2294.74-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)
x86_64-native-bsdapp-gcc
x86_64-native-bsdapp-clang
x86_64-native-bsdapp-gcc+shared
x86_64-native-bsdapp-gcc+debug
OS: SUSE15-64
Kernel Version: 5.3.18-lp152.57-default
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
GCC Version: gcc (SUSE Linux) 7.5.0
Clang Version: 9.0.1
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc
*Build Failed #1:
OS: UB2004-64
Target: x86_64-native-linuxapp-doc
FAILED: doc/guides/html
/usr/bin/python3 ../buildtools/call-sphinx-build.py /usr/bin/sphinx-build 21.02.0-rc0 /root/UB2004-64_K5.4.0_GCC9.3.0/x86_64-native-linuxapp-doc/c551824a6b3045dfad30e0d7f37fa91c/dpdk/doc/guides /root/UB2004-64_K5.4.0_GCC9.3.0/x86_64-native-linuxapp-doc/c551824a6b3045dfad30e0d7f37fa91c/dpdk/x86_64-native-linuxapp-doc/doc/guides -W
Install the sphinx ReadTheDocs theme for improved html documentation layout: https://sphinx-rtd-theme.readthedocs.io/
Warning, treated as error:
/root/UB2004-64_K5.4.0_GCC9.3.0/x86_64-native-linuxapp-doc/c551824a6b3045dfad30e0d7f37fa91c/dpdk/doc/guides/sample_app_ug/ifpga.rst:72:Title underline too short.
Commands Description
-------------------
[2589/2613] Compiling C object app/test/dpdk-test.p/test_ring.c.o
[2590/2613] Compiling C object drivers/libtmp_rte_event_octeontx2.a.p/event_octeontx2_otx2_worker.c.o
[2591/2613] Compiling C object drivers/libtmp_rte_event_octeontx2.a.p/event_octeontx2_otx2_worker_dual.c.o
ninja: build stopped
DPDK STV team
reply other threads:[~2021-01-11 8: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='93cfb9$h0rld3@fmsmga005-auth.fm.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).