Re: AWS lab meson test fails

[Patrick Robb <probb@iol.unh.edu>]

[-- Attachment #1: Type: text/plain, Size: 2185 bytes --]

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:
https://core.dpdk.org/testing/#requesting-a-patch-retest

On Thu, Jun 12, 2025 at 8:38 AM Patrick Robb <probb@iol.unh.edu> wrote:

> Hi Shai,
>
> On Thu, Jun 12, 2025 at 6:20 AM Brandes, Shai <shaibran@amazon.com> wrote:
>
>> Hi Patrick,
>>
>> The failure status appears to be due to an issue applying the patch to
>> the release notes RTS file.
>> We suspect that the patch may have been applied to the incorrect DPDK
>> tree.
>> Could you advise if there is any specific metadata we should be using to
>> determine the correct tree for applying the patch?
>>
>
> Here is the script which should be used to determine the tree to apply the
> patchseries to:
> https://git.dpdk.org/tools/dpdk-ci/tree/tools/pw_maintainers_cli.py
>
> 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:
> https://git.dpdk.org/tools/dpdk-ci/tree/tools/create_series_artifact.py
>
> The process create_series_artifact.py uses is:
>
> 1. Try to apply to the tree suggested by pw_maintainers_cli.py. If
> successful, proceed.
> 2. If there was an apply failure in 1, try to apply again, this time on
> main. If successful, proceed.
> 3. If 1 and 2 failed, indicate that there was an apply failure.
>
> 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).
>
> 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.
>
> Thanks Shai.
>

[-- Attachment #2: Type: text/html, Size: 3174 bytes --]