kernelci: kbuild: transition to available state when complete

Currently, `kbuild` nodes transition to state `done` as soon as they
complete, even though they often have many child nodes running
afterwards. This is confusing as `checkout` nodes first transition to
`available` state, then `closing` (waiting for child nodes to complete)
and only transition to `done` once all child nodes have completed.

This behaviour should be applied to `kbuild` nodes as well, both for
consistency and to be able to easily schedule post-processing jobs (e.g.
by triggering those on the `state: done` event).

Also add a `holdoff` value (10 minutes, identical to `checkout` nodes)
so the corresponding service properly handles state transitions for
those nodes.

Fixes  #2875

Signed-off-by: Arnaud Ferraris <[email protected]>

Author: a-wai

kernelci/kbuild.py

@@ -1058,12 +1058,18 @@ def submit(self, retcode, dry_run=False):
                     kselftest_result = 'pass'
                     break
 
+        if job_result == 'pass':
+            job_state = 'available'
+        else:
+            job_state = 'done'
+
         results = {
             'node': {
                 'name': self._apijobname,
                 'result': job_result,
-                'state': 'done',
+                'state': job_state,
                 'artifacts': af_uri,
+                'holdoff': str(datetime.utcnow() + timedelta(minutes=10)),
             },
             'child_nodes': []
         }