<div dir="ltr"><span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Hello DPDK developers, <span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Currently, various testing labs perform CI testing on new patch series sent to <a href="mailto:dev@dpdk.org">dev@dpdk.org</a> and report their results to <a href="https://patchwork.dpdk.org/project/dpdk/list/">https://patchwork.dpdk.org/project/dpdk/list/</a>. On each series on the patch list, the results appear in the test category contexts for IOL (community lab), GitHub, and LoongSon. <span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">If a reported failure on a series seems suspicious to the patch submitter or maintainer, then there may be an interest in requesting a retest on the series for the failing label(s) in order to verify the failure is not spurious or a false positive. This retest demonstrates to the submitter or maintainer that the failure can be reliably reproduced. Unfortunately, at present, the best way to accomplish this is to reach out to lab maintainers via email or Slack. This is not ideal for developers in need of quick test results. <span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Going forward, CI testing labs will be implementing the option to request retest for their respective test labels on patchwork via emails sent to the dev mailing list. This feature is ready today for labels reported by the UNH-IOL Community Lab, and will soon also be an option for the Github Robot at least. <span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">In order to request a retest on your patch series, send an email reply to one of your series’s patch or cover letter emails with email content of the format used below: <span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Recheck-request: <test names> <span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">The valid delimiter is a comma optionally followed by a space: “,” “, “ <span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Valid examples:<span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Recheck-request: iol-compile-amd64-testing, iol-broadcom-Performance, iol-compile-arm64-testing,<span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Recheck-request: iol-compile-amd64-testing,iol-broadcom-Performance, iol-compile-arm64-testing,<span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Recheck-request: iol-compile-amd64-testing, iol-broadcom-Performance, iol-compile-arm64-testing <span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Invalid examples:<span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Recheck-request: iol-compile-amd64-testing, iol-broadcom-Performance<span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Recheck-request: iol-compile-amd64-testing iol-broadcom-Performance,iol-compile-arm64-testing, <span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Some important notes:<ol style="margin-top:0px;margin-bottom:0px"><li dir="ltr" style="list-style-type:decimal;font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre"><span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">At present, there is only support for retesting the series as it existed when the lab received it. As in, if the lab applied the series on DPDK mainline when the head was commit X, and a retest is requested, then retests will be run using those same sources applied on top of commit X. This is important to note because this means retest requests will not provide a solution to your patch being submitted when the tree is in a “bad state.” Getting test results with your patch applied on the current DPDK mainline could be achieved by re-submitting the patch to the mailing list as a workaround.</li><li dir="ltr" style="list-style-type:decimal;font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre"><span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">For any series submitted earlier than August 2023, you must submit a retest request in reply to a patch email, NOT in reply to a cover letter email.</li><li dir="ltr" style="list-style-type:decimal;font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre"><span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">The initial policy is to accept no more than one retest request per patch series version per lab.</li><li dir="ltr" style="list-style-type:decimal;font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre"><span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(0,0,0);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Your patch should begin to retest within 15 minutes of your request, but wait time is subject to the testing queue just like any other series. As a result, retesting will be slower during peak submission time.</li></ol> <span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(34,34,34);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Improvements we are considering for v2 of the email retesting framework:<ol style="margin-top:0px;margin-bottom:0px"><li dir="ltr" style="list-style-type:decimal;font-size:11pt;font-family:Arial,sans-serif;color:rgb(34,34,34);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre"><span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(34,34,34);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Add in an option to re-apply on the latest commit on DPDK mainline. So, if your patch was originally applied on commit X, and you want to retest, but have it be applied to commit Y (latest), you could specify that. Under these circumstances, we would have to do a retest of all labels, since it would be inappropriate to mix reports for results from different commits.</li><li dir="ltr" style="list-style-type:decimal;font-size:11pt;font-family:Arial,sans-serif;color:rgb(34,34,34);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre"><span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(34,34,34);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Add a policy for vetting retest requesters - so maybe only maintainers, or maybe only maintainers and the submitter, or another set of people. </li><li dir="ltr" style="list-style-type:decimal;font-size:11pt;font-family:Arial,sans-serif;color:rgb(34,34,34);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre"><span style="font-size:11pt;font-family:Arial,sans-serif;color:rgb(34,34,34);background-color:rgb(255,255,255);font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Add in an option to request a retest for next-* branches and/or LTS branches.</li></ol></div>