Email Based Re-Testing Framework

[Thomas Monjalon]

06/06/2023 18:56, Patrick Robb:
> Hello all,
> 
> I'd like to revive the conversation about a request from the community for
> an email based re-testing framework. The idea is that using one
> standardized format, dpdk developers could email the test-report mailing
> list, requesting a rerun on their patch series for "X" set of tests at "Y"
> lab. I think that since patchwork testing labels (ie.
> iol-broadcom-Performance, github-robot: build, loongarch-compilation) are
> already visible on patch pages on patchwork, those labels are the most
> reasonable ones to expect developers to use when requesting a re-test. We
> probably wouldn't want to get any more general than that, like, say,
> rerunning all CI testing for a specific patch series at a specific lab,
> since it would result in a significant amount of "wasted" testing capacity.
> 
> The standard email format those of us at the Community Lab are thinking of
> is like below. Developers would request retests by emailing the test-report
> mailing list with email bodies like:
> 
> [RETEST UNH-IOL]
> iol-abi-testing
> iol-broadcom-Performance

What would be the purpose of [RETEST UNH-IOL]?

We need to specify the patchwork identifier of the patch.

We could make a script similar to the checkpatch run on dpdk.org:
https://git.dpdk.org/tools/dpdk-ci/tree/tests/checkpatch.sh
The easiest way to run it is to make the script as the receiver of the mail.
If the lab can receive the mails from the mailing list,
then just need to filter the retest requests for its own lab.