Waiting for pod kube-system/runner-5vnamnhm-project-7-concurrent-02f2ww to be running, status is Pending
Waiting for pod kube-system/runner-5vnamnhm-project-7-concurrent-02f2ww to be running, status is Pending
Waiting for pod kube-system/runner-5vnamnhm-project-7-concurrent-02f2ww to be running, status is Pending
Waiting for pod kube-system/runner-5vnamnhm-project-7-concurrent-02f2ww to be running, status is Pending
Waiting for pod kube-system/runner-5vnamnhm-project-7-concurrent-02f2ww to be running, status is Pending
Waiting for pod kube-system/runner-5vnamnhm-project-7-concurrent-02f2ww to be running, status is Pending
Waiting for pod kube-system/runner-5vnamnhm-project-7-concurrent-02f2ww to be running, status is Pending
Waiting for pod kube-system/runner-5vnamnhm-project-7-concurrent-02f2ww to be running, status is Pending
Waiting for pod kube-system/runner-5vnamnhm-project-7-concurrent-02f2ww to be running, status is Pending
Waiting for pod kube-system/runner-5vnamnhm-project-7-concurrent-02f2ww to be running, status is Pending
Waiting for pod kube-system/runner-5vnamnhm-project-7-concurrent-02f2ww to be running, status is Pending
Waiting for pod kube-system/runner-5vnamnhm-project-7-concurrent-02f2ww to be running, status is Pending
ERROR: Job failed (system failure): timed out waiting for pod to start
This is occurring frequently for bdcat_notebooks, which defines several parallel jobs. see: https://biodata-integration-tests.net/databiosphere/bdcat_notebooks/-/pipelines/1429