pw: support and use pending states

Russell complains that we flag contest as failing when 99% of the time
it's not his changes that caused it. Maintainers report contest failures
manually. Support reporting pending in NIPA core and use it from contest.

Signed-off-by: Jakub Kicinski <[email protected]>

Author: kuba-moo

core/test.py

@@ -71,6 +71,8 @@ def write_result(self, result_dir, retcode=0, out="", err="", desc=""):
             fp.write("==========\n")
             if retcode == 0:
                 fp.write("%s - OKAY\n" % (self.name, ))
+            elif retcode == 111:
+                fp.write("%s - PENDING\n" % (self.name, ))
             elif retcode == 250:
                 fp.write("%s - WARNING\n" % (self.name, ))
             else:

pw_contest.py

@@ -59,7 +59,7 @@ class Codes:
     Codes.PENDING: PatchworkCheckState.PENDING,
     2: PatchworkCheckState.WARNING,
     3: PatchworkCheckState.WARNING,
-    4: PatchworkCheckState.FAIL,
+    4: PatchworkCheckState.PENDING,
 }
 
 

pw_upload.py

@@ -42,6 +42,8 @@ def __init__(self, test_name: str, root_dir: str, url: str):
                 retcode = f.read()
                 if retcode == "0":
                     self.state = PatchworkCheckState.SUCCESS
+                elif retcode == "111":
+                    self.state = PatchworkCheckState.PENDING
                 elif retcode == "250":
                     self.state = PatchworkCheckState.WARNING
                 else: