config: runtime: kunit: ensure result nodes are in "done" state

Nodes are created in `running` state by default. Recent changes to the
API helper functions copy the `state` field from the node instead of
setting it to `done` by default, meaning result nodes stay `running`
until they time out.

Fix this by making those nodes `done` right from the beginning.

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

Author: a-wai

config/runtime/kunit.jinja2

@@ -30,13 +30,15 @@ class Job(BaseJob):
     def _parse_results(self, group):
         node = {
             'name': group['name'],
+            'state': 'done',
         }
         child_nodes = []
         for test_case in group.get('test_cases', []):
             child_nodes.append({
                 'node': {
                     'name': test_case['name'],
                     'result': RESULT_MAP[test_case['status']],
+                    'state': 'done',
                     'kind': 'test'
                 },
                 'child_nodes': [],
@@ -131,6 +133,7 @@ cd {src_path}
         results = {
             'node': {
                 'result': step_results['exec'][0] or 'fail',
+                'state': 'done',
                 'artifacts': artifacts,
                 'data': {'arch': ARCH if ARCH else 'um'}
             },
@@ -140,6 +143,7 @@ cd {src_path}
                         'kind': 'job' if child_nodes else 'test' ,
                         'name': name,
                         'result': result,
+                        'state': 'done',
                     },
                     'child_nodes': child_nodes,
                 } for name, (result, child_nodes) in step_results.items()