Skip to content

add some tuning to autoscaler to handle case where we're not processing data #1048

add some tuning to autoscaler to handle case where we're not processing data

add some tuning to autoscaler to handle case where we're not processing data #1048

Triggered via pull request November 20, 2023 04:16
Status Failure
Total duration 45m 4s
Artifacts

python_ci.yaml

on: pull_request
code-health
16s
code-health
Matrix: pytest
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 2 warnings
pytest (3.9)
The hosted runner: GitHub Actions 5 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
pytest (3.8)
The hosted runner: GitHub Actions 2 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
pytest (3.10)
The hosted runner: GitHub Actions 4 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
code-health
Unexpected input(s) 'checkName', valid inputs are ['options', 'src', 'jupyter', 'black_args', 'version', 'summary']
code-health
Unexpected input(s) 'checkName', valid inputs are ['args', 'src', 'version']