From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: "Liao, TingtingX" <tingtingx.liao@intel.com>
Cc: "Xu, HailinX" <hailinx.xu@intel.com>,
"Cui, KaixinX" <kaixinx.cui@intel.com>,
ci@dpdk.org
Subject: Re: compilation|FAILURE| pw(142339) sid(32483) job(PER_PATCH_BUILD12580)[v8, 5/5] dts: add API doc generation
Date: Mon, 5 Aug 2024 16:37:51 +0200 [thread overview]
Message-ID: <b587b96d-96ac-414f-9b27-74e55ac21fe0@pantheon.tech> (raw)
In-Reply-To: <PH7PR11MB685972D741E28A656B23EFB692BE2@PH7PR11MB6859.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 12486 bytes --]
On 5. 8. 2024 11:10, Liao, TingtingX wrote:
> Hi Juraj,
>
> 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.
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.
> So can we modify the code? Can we not modify the code in the doc?
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
> _
> _
> Tingting Liao
> ------------------------------------------------------------------------
> *发件人:* Juraj Linkeš <juraj.linkes@pantheon.tech>
> *发送时间:* 2024年8月1日 17:11
> *收件人:* Liao, TingtingX <tingtingx.liao@intel.com>
> *抄送:* Xu, HailinX <hailinx.xu@intel.com>; Cui, KaixinX
> <kaixinx.cui@intel.com>
> *主题:* Re: compilation|FAILURE| pw(142339) sid(32483)
> job(PER_PATCH_BUILD12580)[v8, 5/5] dts: add API doc generation
> On 1. 8. 2024 10:13, Liao, TingtingX wrote:
>
> Hi Juraj,
>
> Hi Liao,
>
>
> The occurrence of this error is due to the need to improve the
> code for applying patches in the CI system.
> But when re running the build test, it was found that there was a
> conflict between the current patch and the main branch.
> Therefore, please prepare a new version of the patch. Thank you.
>
>
>
> 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
>
>
> Tingting Liao
> ------------------------------------------------------------------------
> *发件人:* sys_stv@intel.com <mailto:sys_stv@intel.com>
> <sys_stv@intel.com> <mailto:sys_stv@intel.com>
> *发送时间:* 2024年7月12日 17:19
> *收件人:* test-report@dpdk.org <mailto:test-report@dpdk.org>
> <test-report@dpdk.org> <mailto:test-report@dpdk.org>;
> juraj.linkes@pantheon.tech <mailto:juraj.linkes@pantheon.tech>
> <juraj.linkes@pantheon.tech> <mailto:juraj.linkes@pantheon.tech>
> *主题:* compilation|FAILURE| pw(142339) sid(32483)
> job(PER_PATCH_BUILD12580)[v8, 5/5] dts: add API doc generation
>
> Test-Label: Intel-compilation
> Test-Status: FAILURE
> http://dpdk.org/patch/142339 <http://dpdk.org/patch/142339>
>
> _Compilation issues_
>
> Submitter: Juraj Linkeš <juraj.linkes@pantheon.tech>
> <mailto:juraj.linkes@pantheon.tech>
> Date: 2024-07-12 08:57:24
> Reply_mail: <20240712085724.21065-6-juraj.linkes@pantheon.tech>
> <mailto:20240712085724.21065-6-juraj.linkes@pantheon.tech>
>
> 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 (https://bugs.dpdk.org/show_bug.cgi?id=928
> <https://bugs.dpdk.org/show_bug.cgi?id=928>),
> 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
> (https://github.com/llvm/llvm-project.git
> <https://github.com/llvm/llvm-project.git> 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
>
[-- Attachment #2: Type: text/html, Size: 21810 bytes --]
next parent reply other threads:[~2024-08-05 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a19cdd$1fag4l@orviesa008-auth.jf.intel.com>
[not found] ` <PH7PR11MB68597344FF88B19E9D30C6AC92B22@PH7PR11MB6859.namprd11.prod.outlook.com>
[not found] ` <d2a76a7a-5009-437d-a288-78e6b6b9de9c@pantheon.tech>
[not found] ` <PH7PR11MB685972D741E28A656B23EFB692BE2@PH7PR11MB6859.namprd11.prod.outlook.com>
2024-08-05 14:37 ` Juraj Linkeš [this message]
2024-08-08 3:28 ` Liao, TingtingX
2024-08-08 12:37 ` Patrick Robb
2024-08-12 7:03 ` 回复: " Liao, TingtingX
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=b587b96d-96ac-414f-9b27-74e55ac21fe0@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=ci@dpdk.org \
--cc=hailinx.xu@intel.com \
--cc=kaixinx.cui@intel.com \
--cc=tingtingx.liao@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).