[Inference] Integrate vllm example #1481
KepingYanworkflow_orders_on_pr.yml
on: pull_request
Lint
/
lint
32s
Matrix: Tests / bare-test
Matrix: Tests / docker-test
Matrix: Tests / getting-started-test
Matrix: Tests / setup-test
Annotations
18 errors and 4 warnings
|
Tests / getting-started-test (3.9)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Tests / getting-started-test (3.9)
The operation was canceled.
|
|
Tests / getting-started-test (3.10)
The job was canceled because "_3_9" failed.
|
|
Tests / getting-started-test (3.10)
The operation was canceled.
|
|
Tests / getting-started-test (3.11)
The job was canceled because "_3_9" failed.
|
|
Tests / getting-started-test (3.11)
The operation was canceled.
|
|
Tests / bare-test (3.10)
The job running on runner GitHub Actions 7 has exceeded the maximum execution time of 360 minutes.
|
|
Tests / bare-test (3.10)
The operation was canceled.
|
|
Tests / docker-test (3.9)
The job running on runner GitHub Actions 1 has exceeded the maximum execution time of 360 minutes.
|
|
Tests / docker-test (3.9)
The operation was canceled.
|
|
Tests / docker-test (3.10)
The job running on runner GitHub Actions 6 has exceeded the maximum execution time of 360 minutes.
|
|
Tests / docker-test (3.10)
The operation was canceled.
|
|
Tests / bare-test (3.9)
The job running on runner GitHub Actions 5 has exceeded the maximum execution time of 360 minutes.
|
|
Tests / bare-test (3.9)
The operation was canceled.
|
|
Tests / bare-test (3.11)
The job running on runner GitHub Actions 15 has exceeded the maximum execution time of 360 minutes.
|
|
Tests / bare-test (3.11)
The operation was canceled.
|
|
Tests / docker-test (3.11)
The job running on runner GitHub Actions 19 has exceeded the maximum execution time of 360 minutes.
|
|
Tests / docker-test (3.11)
The operation was canceled.
|
|
Tests / setup-test (3.11)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Tests / setup-test (3.10)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Tests / setup-test (3.9)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Tests / getting-started-test (3.9)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|