[PATCH v2] tools: check for pending test status when parsing emails

[Ali Alnubani]

> -----Original Message-----
> From: Patrick Robb <probb at iol.unh.edu>
> Sent: Friday, May 24, 2024 1:00 AM
> To: ci at dpdk.org
> Cc: aconole at redhat.com; ahassick at iol.unh.edu; NBU-Contact-Thomas
> Monjalon (EXTERNAL) <thomas at monjalon.net>; Ali Alnubani
> <alialnu at nvidia.com>; Patrick Robb <probb at iol.unh.edu>
> Subject: [PATCH v2] tools: check for pending test status when parsing emails
> 
> Today, the community CI infrastructure only uses post-result reporting,
> such as "SUCCESS", "FAILED", and "WARNING".  These results get reported
> only after a test finishes.  This creates some confusion about whether a
> test might have been started for the series in question.  It isn't easy
> to tell at-a-glance which tests are currently running for a given patch
> or series.
> 
> This patch aims to introduce support for a "PENDING" state in the CI
> infrastructure.  This allows labs to indicate which tests have started
> and are awaiting results.  That means test writers should now send a
> "PENDING" status for tests as they start, and then update with a
> post-test result after.  With this change, understanding which tests ran
> at-a-glance is something we can achieve.
> 
> This change should have no affect on the actual tests being run.
> 
> Signed-off-by: Patrick Robb <probb at iol.unh.edu>
> ---

Acked-by: Ali Alnubani <alialnu at nvidia.com>

Thanks,
Ali