From: Patrick Robb <probb@iol.unh.edu>
To: "Puttaswamy, Rajesh T" <rajesh.t.puttaswamy@intel.com>
Cc: "Gao, DaxueX" <daxuex.gao@intel.com>,
ci@dpdk.org, Luca Vizzarro <Luca.Vizzarro@arm.com>
Subject: Intel doc built failure in DPDK CI testing
Date: Thu, 6 Nov 2025 14:50:37 -0500 [thread overview]
Message-ID: <CAJvnSUBZKbPawKqpmWWT-hdLjn14-+vNAC6rwEsRmV-S261=2w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2526 bytes --]
Hello,
I recently submitted a patchseries to DPDK, which Intel DPDK Lab is
reporting a build failure for:
failure email:
https://mails.dpdk.org/archives/test-report/2025-November/927503.html
series: https://patchwork.dpdk.org/project/dpdk/list/?series=36596
failure:
---------------
*Build Failed #1:
OS: UB2404-64
Target: x86_64-native-linuxapp-doc
FAILED: doc/guides/html
/usr/bin/python3 ../buildtools/call-sphinx-build.py /usr/bin/sphinx-build
25.11.0-rc1
/root/UB2404-64_K6.8.0_GCC13.3.0/x86_64-native-linuxapp-doc/36596/dpdk/doc/guides
/root/UB2404-64_K6.8.0_GCC13.3.0/x86_64-native-linuxapp-doc/36596/dpdk/x86_64-native-linuxapp-doc/doc/guides
-a -W
Warning, treated as error:
/root/UB2404-64_K6.8.0_GCC13.3.0/x86_64-native-linuxapp-doc/36596/dpdk/doc/guides/tools/dts.rst:555:Include
file
'/root/UB2404-64_K6.8.0_GCC13.3.0/x86_64-native-linuxapp-doc/36596/dpdk/dts/test_run.example.yaml'
not found or reading it failed
[3674/3674] Generating doc/api/dts/dts_api_html with a custom command
ninja: build stopped
--------------------
The above says the failure is caused because dpdk/dts/test_run.example.yaml
is not found, and it is referenced in line 555 of dts.rst. That makes
sense, given that dts/test_run.example.yaml is removed in my series, and
moved into a new directory (dts/configuration). So, now the path for this
file is dts/configuration/test_run.example.yaml. However, this should not
be an issue for the build, because dts.rest is updated in my patchseries to
reflect the new configuration paths. See:
https://patchwork.dpdk.org/project/dpdk/patch/20251105223628.1659390-3-probb@iol.unh.edu/
diff:
@@ -549,20 +576,20 @@ And they both have two network ports which are
physically connected to each othe
.. _test_run_configuration_example:
-``dts/test_run.example.yaml``
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+``dts/configurations/test_run.example.yaml``
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-.. literalinclude:: ../../../dts/test_run.example.yaml
+.. literalinclude:: ../../../dts/configurations/test_run.example.yaml
:language: yaml
:start-at: # Define
The diff above which is a part of my series should be ensuring that the
reference to dts/test_run.example.yaml is removed, but it is clearly still
remaining in the DPDK artifact you are using for your build for testing.
Can you check this, and check whether my patch is being properly applied
before the doc build starts? Please let me know if I am making any errors,
I am happy to re-submit differently as needed!
Thanks.
[-- Attachment #2: Type: text/html, Size: 3122 bytes --]
reply other threads:[~2025-11-06 19:51 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='CAJvnSUBZKbPawKqpmWWT-hdLjn14-+vNAC6rwEsRmV-S261=2w@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=Luca.Vizzarro@arm.com \
--cc=ci@dpdk.org \
--cc=daxuex.gao@intel.com \
--cc=rajesh.t.puttaswamy@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).