<div dir="ltr">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><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, Jun 12, 2025 at 8:38 AM Patrick Robb <<a href="mailto:probb@iol.unh.edu">probb@iol.unh.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">Hi Shai,<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 12, 2025 at 6:20 AM Brandes, Shai <<a href="mailto:shaibran@amazon.com" target="_blank">shaibran@amazon.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">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?<br></blockquote><div><br></div><div>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></div><div><br></div><div>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></div><div><br></div><div>The process create_series_artifact.py uses is:</div><div><br></div><div>1. Try to apply to the tree suggested by pw_maintainers_cli.py. If successful, proceed.</div><div>2. If there was an apply failure in 1, try to apply again, this time on main. If successful, proceed.</div><div>3. If 1 and 2 failed, indicate that there was an apply failure.</div><div><br></div><div>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).</div><div> </div><div>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.</div><div><br></div><div>Thanks Shai.</div></div></div> </blockquote></div>