<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <div class="moz-cite-prefix">On 5. 8. 2024 11:10, Liao, TingtingX wrote: </div> <blockquote type="cite" cite="mid:PH7PR11MB685972D741E28A656B23EFB692BE2@PH7PR11MB6859.namprd11.prod.outlook.com"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <style type="text/css" style="display:none;">P {margin-top:0;margin-bottom:0;}</style> <div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> Hi Juraj,</div> <div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> </div> <div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> In the CI testing system, the patch build failure is due to the parameter "-- exclude=doc/* *". This parameter does not apply all modifications under doc, causing errors. However, deleting this parameter carries unpredictable risks. </div> </blockquote> Is this a parameter you're using in CI? As I see it, the parameter produces predictable risks, as is the case with this patch, which may be even worse. <blockquote type="cite" cite="mid:PH7PR11MB685972D741E28A656B23EFB692BE2@PH7PR11MB6859.namprd11.prod.outlook.com"> <div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> So can we modify the code? Can we not modify the code in the doc?</div> </blockquote> What code? If you mean the code introduces in the patch, then no, the patch doesn't work with the variable. I think you've got this the other way around. CI can't put any constraints on what code we submit. It should only tell us about the state of the code, which it seems it doesn't if there are parameters that break things. I suggest you figure out a better way to handle this on your end. Juraj <blockquote type="cite" cite="mid:PH7PR11MB685972D741E28A656B23EFB692BE2@PH7PR11MB6859.namprd11.prod.outlook.com"> <div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> </div> <div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> Tingting Liao</div> <hr style="display: inline-block; width: 98%;"> <div id="divRplyFwdMsg" dir="ltr" class="elementToProof">发件人: Juraj Linkeš <a class="moz-txt-link-rfc2396E" href="mailto:juraj.linkes@pantheon.tech"><juraj.linkes@pantheon.tech></a> 发送时间: 2024年8月1日 17:11 收件人: Liao, TingtingX <a class="moz-txt-link-rfc2396E" href="mailto:tingtingx.liao@intel.com"><tingtingx.liao@intel.com></a> 抄送: Xu, HailinX <a class="moz-txt-link-rfc2396E" href="mailto:hailinx.xu@intel.com"><hailinx.xu@intel.com></a>; Cui, KaixinX <a class="moz-txt-link-rfc2396E" href="mailto:kaixinx.cui@intel.com"><kaixinx.cui@intel.com></a> 主题: Re: compilation|FAILURE| pw(142339) sid(32483) job(PER_PATCH_BUILD12580)[v8, 5/5] dts: add API doc generation <div> </div> </div> <div class="elementToProof">On 1. 8. 2024 10:13, Liao, TingtingX wrote:</div> <blockquote> <div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> Hi Juraj,</div> <div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> </div> </blockquote> Hi Liao, <blockquote> <div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> The occurrence of this error is due to the need to improve the code for applying patches in the CI system.</div> <div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> But when re running the build test, it was found that there was a conflict between the current patch and the main branch.</div> <div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> Therefore, please prepare a new version of the patch. Thank you.</div> <div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> </div> </blockquote> Great, I'll send a new version. Do I understand it right that you first need to fix the apply issues on your side before it could be passing? So I send the my updated version, then you fix the issue and then what? Thanks, Juraj <blockquote> <div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);"> Tingting Liao</div> <hr style="display: inline-block; width: 98%;"> <div id="x_divRplyFwdMsg" dir="ltr">发件人: <a href="mailto:sys_stv@intel.com" id="OWA8e07e27e-0a27-cd10-1895-da3b4cb9b449" class="x_moz-txt-link-abbreviated OWAAutoLink moz-txt-link-freetext" moz-do-not-send="true">sys_stv@intel.com</a> <a href="mailto:sys_stv@intel.com" id="OWA64e5d4db-4402-663d-6c6a-4094971327e4" class="x_moz-txt-link-rfc2396E OWAAutoLink" moz-do-not-send="true"> <sys_stv@intel.com></a> 发送时间: 2024年7月12日 17:19 收件人: <a href="mailto:test-report@dpdk.org" id="OWA2554928a-8e0a-889b-98fc-ed02b7588f7b" class="x_moz-txt-link-abbreviated OWAAutoLink moz-txt-link-freetext" moz-do-not-send="true">test-report@dpdk.org</a> <a href="mailto:test-report@dpdk.org" id="OWA413250a2-49e7-4303-942a-48ec3e80c918" class="x_moz-txt-link-rfc2396E OWAAutoLink" moz-do-not-send="true"> <test-report@dpdk.org></a>; <a href="mailto:juraj.linkes@pantheon.tech" id="OWA027cf47d-12ff-15a5-5bd1-708a82686aa6" class="x_moz-txt-link-abbreviated OWAAutoLink moz-txt-link-freetext" moz-do-not-send="true"> juraj.linkes@pantheon.tech</a> <a href="mailto:juraj.linkes@pantheon.tech" id="OWAa079bbd8-91be-acbf-2e9e-f859dae8750f" class="x_moz-txt-link-rfc2396E OWAAutoLink" moz-do-not-send="true"> <juraj.linkes@pantheon.tech></a> 主题: compilation|FAILURE| pw(142339) sid(32483) job(PER_PATCH_BUILD12580)[v8, 5/5] dts: add API doc generation <div> </div> </div> <div class="elementToProof" style="font-size: 11pt;"> Test-Label: Intel-compilation Test-Status: FAILURE <a href="http://dpdk.org/patch/142339" id="OWA86c90aa1-be4e-feca-01dd-d259fddd879b" class="x_OWAAutoLink x_moz-txt-link-freetext moz-txt-link-freetext" data-auth="NotApplicable" moz-do-not-send="true">http://dpdk.org/patch/142339</a> _Compilation issues_ Submitter: Juraj Linkeš <a href="mailto:juraj.linkes@pantheon.tech" id="OWA423715dc-cf9b-ec92-4b62-8377db019024" class="x_moz-txt-link-rfc2396E OWAAutoLink" moz-do-not-send="true"> <juraj.linkes@pantheon.tech></a> Date: 2024-07-12 08:57:24 Reply_mail: <a href="mailto:20240712085724.21065-6-juraj.linkes@pantheon.tech" id="OWAa614e9b2-1fe4-38dd-020d-74fba7cb643b" class="x_moz-txt-link-rfc2396E OWAAutoLink" moz-do-not-send="true"> <20240712085724.21065-6-juraj.linkes@pantheon.tech></a> DPDK git baseline: Repo:dpdk-next-baseband, CommitID: 76fa7797c09d5b6bb4aaed8a8f48a3afd6fb2548 Meson Build Summary: 23 Builds Done, 18 Successful, 5 Failures, 0 Blocked +-------------------+------------+--------------+------------+------------+-----------+----------+------------+ | os | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document | gcc-16byte | +-------------------+------------+--------------+------------+------------+-----------+----------+------------+ | OpenAnolis8.8-64 | pass | | | | | | | | FreeBSD14-64 | pass | pass | | pass | pass | | | | RHEL94-64 | pass | pass | | pass | pass | | | | SUSE15-64 | pass | pass | | | | | | | CBL-Mariner2.0-64 | pass | | | | | | | | UB2404-32 | pass | | | | | | | | RHEL93-64 | pass | | | | | | | | UB2404-64 | fail | fail | | | | fail | fail | | RHEL94-64Rt | pass | | | | | | | | UB2204-64 | pass | | | | | | | | FC40-64 | pass | pass | | | | | | | UB2404-64Rt | fail | | | | | | | +-------------------+------------+--------------+------------+------------+-----------+----------+------------+ Comments: Because of DPDK bug (<a href="https://bugs.dpdk.org/show_bug.cgi?id=928" id="OWA1d2c179c-96d5-9aa1-74f4-89b431706e8a" class="x_OWAAutoLink x_moz-txt-link-freetext moz-txt-link-freetext" data-auth="NotApplicable" moz-do-not-send="true">https://bugs.dpdk.org/show_bug.cgi?id=928</a>), All the dpdk-next-* branch add `Ddisable_drivers=event/cnxk` option when build with ICC complier. Test environment and configuration as below: OS: OpenAnolis8.8-64 Kernel Version: 5.10.134-13.an8.x86_64 GCC Version: gcc (GCC) 8.5.0 20210514 (Anolis 8.5.0-10.0.3) Clang Version: 13.0.1 (Anolis 13.0.1-2.0.2.module+an8.7.0+10996+1588f068) x86_64-native-linuxapp-gcc OS: FreeBSD14-64 Kernel Version: 14.0-RELEASE GCC Version: gcc (FreeBSD Ports Collection) 12.2.0 Clang Version: 16.0.6 (<a href="https://github.com/llvm/llvm-project.git" id="OWAbb0cf25f-a875-4cb6-7a41-acd89297d66e" class="x_moz-txt-link-freetext OWAAutoLink moz-txt-link-freetext" data-auth="NotApplicable" moz-do-not-send="true">https://github.com/llvm/llvm-project.git</a> llvmorg-16.0.6-0-g7cbf1a259152) x86_64-native-bsdapp-gcc x86_64-native-bsdapp-clang x86_64-native-bsdapp-gcc+shared x86_64-native-bsdapp-gcc+debug OS: RHEL94-64 Kernel Version: 5.14.0-427.13.1.el9_4.x86_64 GCC Version: gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3) Clang Version: 17.0.6 (Red Hat, Inc. 17.0.6-5.el9) x86_64-native-linuxapp-gcc x86_64-native-linuxapp-clang x86_64-native-linuxapp-gcc+shared x86_64-native-linuxapp-gcc+debug OS: SUSE15-64 Kernel Version: 5.14.21-150500.53-default GCC Version: gcc (SUSE Linux) 7.5.0 Clang Version: 15.0.7 x86_64-native-linuxapp-clang x86_64-native-linuxapp-gcc OS: CBL-Mariner2.0-64 Kernel Version: 5.15.55.1_2e9a4f9+ GCC Version: gcc (GCC) 11.2.0 Clang Version: NA x86_64-native-linuxapp-gcc OS: UB2404-32 Kernel Version: 6.8.0-31-generic GCC Version: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0 Clang Version: NA i686-native-linuxapp-gcc OS: RHEL93-64 Kernel Version: 5.14.0-362.8.1.el9_3.x86_64 GCC Version: gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3) Clang Version: 17.0.6 (Red Hat, Inc. 17.0.6-5.el9) x86_64-native-linuxapp-gcc OS: UB2404-64 Kernel Version: 6.8.0-31-generic GCC Version: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0 Clang Version: 18.1.3 (1) x86_64-native-linuxapp-gcc+16byte x86_64-native-linuxapp-gcc x86_64-native-linuxapp-clang x86_64-native-linuxapp-doc OS: RHEL94-64Rt Kernel Version: 5.14.0-427.13.1.el9_4.x86_64+rt GCC Version: gcc (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3) Clang Version: 17.0.6 (Red Hat, Inc. 17.0.6-5.el9) x86_64-native-linuxapp-gcc OS: UB2204-64 Kernel Version: 5.15.0-94-generic GCC Version: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0 Clang Version: 14.0.0-1ubuntu1.1 x86_64-native-linuxapp-gcc OS: FC40-64 Kernel Version: 6.8.5-301.fc40.x86_64 GCC Version: gcc (GCC) 14.0.1 20240411 (Red Hat 14.0.1-0) Clang Version: 18.1.1 (Fedora 18.1.1-1.fc40) x86_64-native-linuxapp-gcc x86_64-native-linuxapp-clang OS: UB2404-64Rt Kernel Version: 6.8.0-rt8 GCC Version: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0 Clang Version: 18.1.3 (1) x86_64-native-linuxapp-gcc *Build Failed #1: OS: UB2404-64 Target: x86_64-native-linuxapp-gcc+16byte Program sphinx-build found: YES (/usr/bin/sphinx-build) Program sphinx-apidoc found: YES (/usr/bin/sphinx-apidoc) dts/doc/meson.build:11:0: ERROR: Unknown variable "doc_api_build_dir". A full log can be found at /root/UB2404-64_K6.8.0_GCC13.2.0/x86_64-native-linuxapp-gcc+16byte/32483/dpdk/x86_64-native-linuxapp-gcc+16byte/meson-logs/meson-log.txt *Build Failed #2: OS: UB2404-64 Target: x86_64-native-linuxapp-gcc Program sphinx-build found: YES (/usr/bin/sphinx-build) Program sphinx-apidoc found: YES (/usr/bin/sphinx-apidoc) dts/doc/meson.build:11:0: ERROR: Unknown variable "doc_api_build_dir". A full log can be found at /root/UB2404-64_K6.8.0_GCC13.2.0/x86_64-native-linuxapp-gcc/32483/dpdk/x86_64-native-linuxapp-gcc/meson-logs/meson-log.txt *Build Failed #3: OS: UB2404-64 Target: x86_64-native-linuxapp-clang Program sphinx-build found: YES (/usr/bin/sphinx-build) Program sphinx-apidoc found: YES (/usr/bin/sphinx-apidoc) dts/doc/meson.build:11:0: ERROR: Unknown variable "doc_api_build_dir". A full log can be found at /root/UB2404-64_K6.8.0_Clang18.1.3/x86_64-native-linuxapp-clang/32483/dpdk/x86_64-native-linuxapp-clang/meson-logs/meson-log.txt *Build Failed #4: OS: UB2404-64 Target: x86_64-native-linuxapp-doc Program sphinx-build found: YES (/usr/bin/sphinx-build) Program sphinx-apidoc found: YES (/usr/bin/sphinx-apidoc) dts/doc/meson.build:11:0: ERROR: Unknown variable "doc_api_build_dir". A full log can be found at /root/UB2404-64_K6.8.0_GCC13.2.0/x86_64-native-linuxapp-doc/32483/dpdk/x86_64-native-linuxapp-doc/meson-logs/meson-log.txt *Build Failed #5: OS: UB2404-64Rt Target: x86_64-native-linuxapp-gcc Program sphinx-build found: YES (/usr/bin/sphinx-build) Program sphinx-apidoc found: YES (/usr/bin/sphinx-apidoc) dts/doc/meson.build:11:0: ERROR: Unknown variable "doc_api_build_dir". A full log can be found at /root/UB2404-64Rt_K6.8.0_GCC13.2.0/x86_64-native-linuxapp-gcc/32483/dpdk/x86_64-native-linuxapp-gcc/meson-logs/meson-log.txt DPDK STV team</div> </blockquote> </blockquote> </body> </html>