[PATCH v2] tools: check for pending test status when parsing emails
Patrick Robb
probb at iol.unh.edu
Thu May 23 23:59:45 CEST 2024
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>
---
tools/update-pw.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/update-pw.sh b/tools/update-pw.sh
index 07067dd..b0f0baa 100755
--- a/tools/update-pw.sh
+++ b/tools/update-pw.sh
@@ -49,6 +49,7 @@ case $status in
'SUCCESS') pwstatus='success' ;;
'WARNING') pwstatus='warning' ;;
'FAILURE') pwstatus='fail' ;;
+ 'PENDING') pwstatus='pending' ;;
esac
printf 'id = %s\nlabel = %s\nstatus = %s/%s %s\nurl = %s\n' \
"$pwid" "$label" "$status" "$pwstatus" "$desc" "$url"
--
2.40.0
More information about the ci
mailing list