From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id AEC2B48A86; Thu, 6 Nov 2025 20:51:47 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A92784021F; Thu, 6 Nov 2025 20:51:47 +0100 (CET) Received: from mail-pl1-f181.google.com (mail-pl1-f181.google.com [209.85.214.181]) by mails.dpdk.org (Postfix) with ESMTP id 8AB9D4013F for ; Thu, 6 Nov 2025 20:51:46 +0100 (CET) Received: by mail-pl1-f181.google.com with SMTP id d9443c01a7336-294fe7c2e69so145145ad.0 for ; Thu, 06 Nov 2025 11:51:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1762458706; x=1763063506; darn=dpdk.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=h8WyoAglg9bhwVkVyDGYFw86IlDJ3Z0UA/8145mgV3w=; b=cstRbJHFpr/3yfMTzK4r6FKkbP7xpJO6avNR2Hali7FxWW+ar6n1ZPY3KFFV8XLwTl ey/GO0KhgE0cwLfQBfwRnacfWNL7zWH1Hf0XuOuVvIpXGyAABTBZXJaVqLWLqmH6gq+y x2wEOkyOn+Tpzn2FVCWPLmpO2KgcgYLb8gGno= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1762458706; x=1763063506; h=cc:to:subject:message-id:date:from:mime-version:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=h8WyoAglg9bhwVkVyDGYFw86IlDJ3Z0UA/8145mgV3w=; b=uGV05Kn+OZXdPYY2GbPA9fM/7ylQYrlFnNdUTf4t0Aox3g7sWNzExU6zs9l9MhZheE Qtx1bONMD7OR3G5sZaV4u5qrXeMq/tLGx9zS/DekbIQcuaZDLW5TmYFp+JEGHq4DDJKO 6J+bLMHFlwib6PxBfSI3SMieEp+A2+cXSml2TnL+wQlKuOb42sfnPEwAjjbnE5peKHOW XTICyrPnAxNp7kMn37pKoamZPlEet6o7471FPDvi6kfFkkf6TqMCdKl2fjgZhlgXthCW /SVhRGWer4SwLrcrTuqJ+HC9MoASup0ISdtQp634eQc2qE4Krfl8ZAcN0w+sryP91Jmj 9Jmg== X-Forwarded-Encrypted: i=1; AJvYcCVbAEUGqAheO/0kFOVWVA0vkB0zayMekiJD/FEBp3cACuwE5pHfFQAOd80hs2W4IjpX1A==@dpdk.org X-Gm-Message-State: AOJu0YxgJmTK/hs14yaIYmcJ6Url+pxDSoGIhfCQav+9bov2pSoIWLgg ZxVsERVXnvGcf9JXMJyiPCPfIiB/Aq9+0tdEDdoImBiI30Zh5cf7my0AQISYfn+ejZojOwMoa3B rALKUHUCOZQBFh0Dv4nKLg+88YZjtyUvlYA9dzO2dBg== X-Gm-Gg: ASbGncvlnVb9dQN2D/iEhC+G8UOdARnzJLKgxVB5Mq23mzcUL3GIrfkf8NdT8ta5dQp T+JWt7QePhODrRHSVzLYGpYYhScwuyVyNXO1nR14FjifwBXl41KjsIB9pz/gAtAucAyyjj4/Mzm USiUae4KK7RGh5fXNrDtwJ9aTagfxgTlYYpAsW3Tp7SVh69dZXXgzKGfycaMwWhtR1x1QX17Qbl 6QIW+nI+lIh2xa0oHSQPnULuLdy6mYzNFA7de5JXqOenUxLrGZg3fB7T0y9RwnWQ6TOTdTpoIZv mg2uijLGIXIWGanGtPtExWrN2cfy X-Google-Smtp-Source: AGHT+IE24c0N9BBdjpwGPdVbKBKD1izvKvkqBKnyZOclQ24P5Vu88xv4icCx/fJeu4/6JjGuSZLBmCLYBf4OwhbCTWM= X-Received: by 2002:a17:902:d507:b0:295:9b9a:6a7f with SMTP id d9443c01a7336-297c0464c66mr8929685ad.49.1762458705538; Thu, 06 Nov 2025 11:51:45 -0800 (PST) MIME-Version: 1.0 From: Patrick Robb Date: Thu, 6 Nov 2025 14:50:37 -0500 X-Gm-Features: AWmQ_bmAvqNOL8SlMV64JZtLWnx6lUlw2oYB27XvAPEw17gsj0J7ecneSiseXO8 Message-ID: Subject: Intel doc built failure in DPDK CI testing To: "Puttaswamy, Rajesh T" Cc: "Gao, DaxueX" , ci@dpdk.org, Luca Vizzarro Content-Type: multipart/alternative; boundary="000000000000133f600642f2658c" X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org --000000000000133f600642f2658c Content-Type: text/plain; charset="UTF-8" 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. --000000000000133f600642f2658c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

I recently submitted = a patchseries to DPDK, which Intel DPDK Lab is reporting a build failure fo= r:


failure:=C2=A0

---------------

*Build Failed = #1:
OS: UB2404-64
Target: x86_64-native-linuxapp-doc
FAILED: doc/g= uides/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-li= nuxapp-doc/36596/dpdk/doc/guides /root/UB2404-64_K6.8.0_GCC13.3.0/x86_64-na= tive-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 &#= 39;/root/UB2404-64_K6.8.0_GCC13.3.0/x86_64-native-linuxapp-doc/36596/dpdk/d= ts/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 ca= used because=C2=A0dpdk/dts/test_run.example.yaml is not found, and it is re= ferenced 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/c= onfiguration). 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=C2=A0to reflect the new configuration= paths. See:=C2=A0https://patchwork.dpdk.org/pro= ject/dpdk/patch/20251105223628.1659390-3-probb@iol.unh.edu/
<= br>
diff:=C2=A0

@@ -549,20 +576,20 @@ = =C2=A0And they both have two network ports which are physically connected t= o each othe
=C2=A0
=C2=A0.. _test_run_configuration_example:
=C2= =A0
-``dts/test_run.example.yaml``
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+``dts/configurations/test_run.example.yaml``
+~~~~~~~~~~~~~~~~~~~~~~~~= ~~~~~~~~~~~~~~~~~~~~
=C2=A0
-.. literalinclude:: ../../../dts/test_ru= n.example.yaml
+.. literalinclude:: ../../../dts/configurations/test_run= .example.yaml
=C2=A0 =C2=A0 :language: yaml
=C2=A0 =C2=A0 :start-at: = # Define
=C2=A0

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 whethe= r my patch is being properly applied before the doc build starts? Please le= t me know if I am making any errors, I am happy to re-submit differently as= needed!=C2=A0

Thanks.
--000000000000133f600642f2658c--