<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word"> <div class="WordSection1"> <p class="MsoNormal">Thanks for the detailed response, adding Wajeeh, who maintains the lab<o:p></o:p></p> <p class="MsoNormal"><o:p> </o:p></p> <div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt"> <div> <div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in"> <p class="MsoNormal"><b>From:</b> Patrick Robb <probb@iol.unh.edu> <br> <b>Sent:</b> Thursday, June 12, 2025 3:43 PM<br> <b>To:</b> Brandes, Shai <shaibran@amazon.com><br> <b>Cc:</b> Bruce Richardson <bruce.richardson@intel.com>; ci@dpdk.org<br> <b>Subject:</b> RE: [EXTERNAL] AWS lab meson test fails<o:p></o:p></p> </div> </div> <p class="MsoNormal"><o:p> </o:p></p> <div> <table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse"> <tbody> <tr style="height:15.25pt"> <td width="1123" valign="top" style="width:842.35pt;border:solid #ED7D31 1.5pt;padding:0in 5.4pt 0in 5.4pt;height:15.25pt"> <p><strong><span style="font-family:"Calibri",sans-serif;color:black;background:#FFFF99">CAUTION</span></strong><span style="color:black;background:#FFFF99">: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.</span><o:p></o:p></p> </td> </tr> </tbody> </table> </div> <p class="MsoNormal"><o:p> </o:p></p> <div> <div> <p class="MsoNormal">Oh, and of course I'll just raise that if the apply failure comes from pw_maintainers_cli.py having guessed the wrong tree, the submitter can always request a rebase and retest on a particular branch (which they can specify) using the testing recheck framework: <a href="https://core.dpdk.org/testing/#requesting-a-patch-retest">https://core.dpdk.org/testing/#requesting-a-patch-retest</a><o:p></o:p></p> </div> <p class="MsoNormal"><o:p> </o:p></p> <div> <div> <p class="MsoNormal">On Thu, Jun 12, 2025 at 8:38 AM Patrick Robb <<a href="mailto:probb@iol.unh.edu">probb@iol.unh.edu</a>> wrote:<o:p></o:p></p> </div> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"> <div> <div> <p class="MsoNormal">Hi Shai,<o:p></o:p></p> </div> <p class="MsoNormal"><o:p> </o:p></p> <div> <div> <p class="MsoNormal">On Thu, Jun 12, 2025 at 6:20 AM Brandes, Shai <<a href="mailto:shaibran@amazon.com" target="_blank">shaibran@amazon.com</a>> wrote:<o:p></o:p></p> </div> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"> <p class="MsoNormal">Hi Patrick,<br> <br> The failure status appears to be due to an issue applying the patch to the release notes RTS file.<br> We suspect that the patch may have been applied to the incorrect DPDK tree.<br> Could you advise if there is any specific metadata we should be using to determine the correct tree for applying the patch?<o:p></o:p></p> </blockquote> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal">Here is the script which should be used to determine the tree to apply the patchseries to: <a href="https://git.dpdk.org/tools/dpdk-ci/tree/tools/pw_maintainers_cli.py" target="_blank">https://git.dpdk.org/tools/dpdk-ci/tree/tools/pw_maintainers_cli.py</a><o:p></o:p></p> </div> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal">Even better than using that directly, though, is using this create series artifact script, which will handle running pw_maintainers_cli.py and applying the series from patchwork for you: <a href="https://git.dpdk.org/tools/dpdk-ci/tree/tools/create_series_artifact.py" target="_blank">https://git.dpdk.org/tools/dpdk-ci/tree/tools/create_series_artifact.py</a><o:p></o:p></p> </div> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal">The process create_series_artifact.py uses is:<o:p></o:p></p> </div> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal">1. Try to apply to the tree suggested by pw_maintainers_cli.py. If successful, proceed.<o:p></o:p></p> </div> <div> <p class="MsoNormal">2. If there was an apply failure in 1, try to apply again, this time on main. If successful, proceed.<o:p></o:p></p> </div> <div> <p class="MsoNormal">3. If 1 and 2 failed, indicate that there was an apply failure.<o:p></o:p></p> </div> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal">Also, if your automation failed to apply the patch, the best thing is to report "_apply patch failure_" in your test_report email, and bail out of running testing (so don't run meson test in this case).<o:p></o:p></p> </div> <div> <p class="MsoNormal"> <o:p></o:p></p> </div> <div> <p class="MsoNormal">And then as a separate matter, I see you mentioned the same sort of .rst apply failure situation was seen on a patch you submitted recently. We do not currently have a strategy for mitigating this, but perhaps we should develop one. Do you have any ideas? I can also raise this discussion during the CI meeting.<o:p></o:p></p> </div> <div> <p class="MsoNormal"><o:p> </o:p></p> </div> <div> <p class="MsoNormal">Thanks Shai.<o:p></o:p></p> </div> </div> </div> </blockquote> </div> </div> </div> </div> </body> </html>