Skip to content
code quality checks and unit tests

negative range seems to work #30

Sign in to view logs

negative range seems to work

negative range seems to work #30

Re-run triggered April 18, 2024 08:08
@alexgarelalexgarel
#101
mesemus:negative-range
Status Failure
Total duration 37s
Artifacts –

test.yml

on: pull_request
Matrix: quality_checks
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 2 warnings
quality_checks (3.8, 7.17.6, 7.4.0)
Process completed with exit code 2.
quality_checks (3.10, 7.17.6, 7.4.0)
Process completed with exit code 2.
quality_checks (3.10, 6.8.23, 6.4.0)
The job was canceled because "_3_8_7_17_6_7_4_0" failed.
quality_checks (3.10, 6.8.23, 6.4.0)
Process completed with exit code 2.
quality_checks (3.9, 7.17.6, 7.4.0)
The job was canceled because "_3_8_7_17_6_7_4_0" failed.
quality_checks (3.9, 7.17.6, 7.4.0)
Process completed with exit code 2.
quality_checks (3.11, 7.17.6, 7.4.0)
The job was canceled because "_3_8_7_17_6_7_4_0" failed.
quality_checks (3.11, 7.17.6, 7.4.0)
The operation was canceled.
quality_checks (3.8, 7.17.6, 7.4.0)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
quality_checks (3.10, 7.17.6, 7.4.0)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-python@v4. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.