From: "Tummala, Sivaprasad" <Sivaprasad.Tummala@amd.com>
To: "sys_stv@intel.com" <sys_stv@intel.com>,
"test-report@dpdk.org" <test-report@dpdk.org>
Subject: RE: compilation|FAILURE| pw(146826) sid(33620) job(PER_PATCH_BUILD13800)[v9,6/6] power: rename library sources for cpu frequency management
Date: Fri, 25 Oct 2024 06:44:33 +0000 [thread overview]
Message-ID: <CH3PR12MB823379E4A6C5FD40F59BAD48864F2@CH3PR12MB8233.namprd12.prod.outlook.com> (raw)
In-Reply-To: <7206a3$2ca4vq@orviesa010-auth.jf.intel.com>
[AMD Official Use Only - AMD Internal Distribution Only]
Hello Intel STV team,
Looking at the logs, this seems to be a false positive and the issue is already fixed in the patch.
Can you please re-check this and let me know for any issues.
Thanks & Regards,
Sivaprasad
> -----Original Message-----
> From: sys_stv@intel.com <sys_stv@intel.com>
> Sent: Wednesday, October 23, 2024 11:06 AM
> To: test-report@dpdk.org; Tummala, Sivaprasad
> <Sivaprasad.Tummala@amd.com>
> Subject: compilation|FAILURE| pw(146826) sid(33620)
> job(PER_PATCH_BUILD13800)[v9,6/6] power: rename library sources for cpu
> frequency management
>
> Caution: This message originated from an External Source. Use proper caution
> when opening attachments, clicking links, or responding.
>
>
> Test-Label: Intel-compilation
> Test-Status: FAILURE
> http://dpdk.org/patch/146826
>
> _Compilation issues_
>
> Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
> Date: 2024-10-23 05:11:38
> Reply_mail: <20241023051139.1066426-7-sivaprasad.tummala@amd.com>
>
> DPDK git baseline: Repo:dpdk, CommitID:
> 3ee7a3e0e0e0f5a81a4b102a834697bc488fb32f
>
>
> Meson Build Summary: 23 Builds Done, 22 Successful, 1 Failures, 0 Blocked
>
> +------------------+------------+--------------+------------+------------+-----------+----------+-----
> -------+
> | os | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug |
> document | gcc-16byte |
> +------------------+------------+--------------+------------+------------+-----------+----------+-----
> -------+
> | OpenAnolis8.9-64 | pass | | | | | | |
> | FreeBSD14-64 | pass | pass | | pass | pass | |
> |
> | RHEL94-64 | pass | pass | | pass | pass | |
> |
> | SUSE15-64 | pass | pass | | | | | |
> | AzureLinux3.0-64 | pass | | | | | | |
> | UB2404-32 | pass | | | | | | |
> | RHEL8.10-64 | pass | | | | | | |
> | UB2404-64 | pass | pass | | | | fail | pass |
> | RHEL94-64Rt | pass | | | | | | |
> | UB2410-64 | pass | | | | | | |
> | FC40-64 | pass | pass | | | | | |
> | UB2404-64Rt | pass | | | | | | |
> +------------------+------------+--------------+------------+------------+-----------+----------+-----
> -------+
>
> Comments:
> Because of DPDK bug (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.9-64
> Kernel Version: 5.10.134-16.2.an8.x86_64
> GCC Version: gcc (GCC) 8.5.0 20210514 (Anolis 8.5.0-22.0.1)
> Clang Version: 15.0.7 (Anolis 15.0.7-1.0.3.module+an8.8.0+11135+e398acfc)
> x86_64-native-linuxapp-gcc
>
> OS: FreeBSD14-64
> Kernel Version: 14.1-RELEASE
> GCC Version: gcc (FreeBSD Ports Collection) 13.2.0
> Clang Version: 18.1.5 (https://github.com/llvm/llvm-project.git llvmorg-18.1.5-0-
> g617a15a9eac9)
> 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: 6.4.0-150600.21-default
> GCC Version: gcc (SUSE Linux) 7.5.0
> Clang Version: 17.0.6
> x86_64-native-linuxapp-clang
> x86_64-native-linuxapp-gcc
>
> OS: AzureLinux3.0-64
> Kernel Version: 6.6.47.1-1.azl3
> GCC Version: gcc (GCC) 13.2.0
> Clang Version: 18.1.2
> x86_64-native-linuxapp-gcc
>
> OS: UB2404-32
> Kernel Version: 6.8.0-41-generic
> GCC Version: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
> Clang Version: NA
> i686-native-linuxapp-gcc
>
> OS: RHEL8.10-64
> Kernel Version: 4.18.0-553.el8_10.x86_64
> GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-21)
> Clang Version: 17.0.6 (Red Hat 17.0.6-1.module+el8.10.0+20808+e12784c0)
> x86_64-native-linuxapp-gcc
>
> OS: UB2404-64
> Kernel Version: 6.8.0-41-generic
> GCC Version: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
> Clang Version: NA
> 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: UB2410-64
> Kernel Version: 6.11.0-8-generic
> GCC Version: gcc (Ubuntu 14.2.0-4ubuntu2) 14.2.0
> Clang Version: NA
> 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: NA
> x86_64-native-linuxapp-gcc
>
>
>
> *Build Failed #1:
> OS: UB2404-64
> Target: x86_64-native-linuxapp-doc
> FAILED: doc/api/html
> /usr/bin/python3 ../doc/api/generate_doxygen.py doc/api/html /usr/bin/doxygen
> doc/api/doxy-api-html.conf
> /root/UB2404-64_K6.8.0_GCC13.2.0/x86_64-native-linuxapp-
> doc/33620/dpdk/doc/api/doxy-api-index.md:105: error: unable to resolve reference
> to 'rte_power.h' for \ref command (warning treated as error, aborting now)
> Traceback (most recent call last):
> File "/root/UB2404-64_K6.8.0_GCC13.2.0/x86_64-native-linuxapp-
> doc/33620/dpdk/x86_64-native-linuxapp-doc/../doc/api/generate_doxygen.py", line
> 13, in <module>
> subprocess.run(doxygen_command, check=True, stdout=out)
> File "/usr/lib/python3.12/subprocess.py", line 571, in run
> raise CalledProcessError(retcode, process.args,
> subprocess.CalledProcessError: Command '['/usr/bin/doxygen', 'doc/api/doxy-api-
> html.conf']' returned non-zero exit status 1.
> [3093/3098] Compiling C object app/dpdk-test.p/test_test_ring.c.o
> [3094/3098] Compiling C object app/dpdk-test.p/test_test_trace_perf.c.o
> [3095/3098] Compiling C object app/dpdk-test.p/test_test_ring_perf.c.o
> [3096/3098] Generating doc/api/dts/dts_api_html with a custom command Install the
> sphinx ReadTheDocs theme for improved html documentation layout:
> https://sphinx-rtd-theme.readthedocs.io/
> [3097/3098] Generating doc/guides/html_guides with a custom command Install the
> sphinx ReadTheDocs theme for improved html documentation layout:
> https://sphinx-rtd-theme.readthedocs.io/
> ninja: build stopped
>
>
> DPDK STV team
prev parent reply other threads:[~2024-10-25 7:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 5:36 compilation|FAILURE| pw(146826) sid(33620) job(PER_PATCH_BUILD13800)[v9, 6/6] " sys_stv
2024-10-25 6:44 ` Tummala, Sivaprasad [this message]
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=CH3PR12MB823379E4A6C5FD40F59BAD48864F2@CH3PR12MB8233.namprd12.prod.outlook.com \
--to=sivaprasad.tummala@amd.com \
--cc=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).