Skip to content

add a faster way to get resource allocation status than sched.resource-status RPC #8481

add a faster way to get resource allocation status than sched.resource-status RPC

add a faster way to get resource allocation status than sched.resource-status RPC #8481

Triggered via pull request March 21, 2024 20:17
Status Failure
Total duration 1h 32m 25s
Artifacts

main.yml

on: pull_request
python linting
30s
python linting
Generate build matrix
9s
Generate build matrix
validate commits
9s
validate commits
spelling
6s
spelling
Matrix: ci-checks
Generate docker manifest
0s
Generate docker manifest
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 2 warnings
jammy - test-install
The job running on runner GitHub Actions 13 has exceeded the maximum execution time of 90 minutes.
jammy - test-install: t/t4000-issues-test-driver.t#L1
not ok 32 - t2492-shell-lost
jammy - test-install: t/t4000-issues-test-driver.t#L1
ERROR: t4000-issues-test-driver.t - exited with status 1
jammy - test-install
Detected 1 missing missing tests:
jammy - test-install
The operation was canceled.
python linting
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
jammy - test-install
Found 1 errors from 404 tests in testsuite