Skip to content

fix: charachter function #574

fix: charachter function

fix: charachter function #574

Triggered via push March 5, 2024 06:58
Status Failure
Total duration 48s
Artifacts

python.yaml

on: push
Virtual Environment
5s
Virtual Environment
Linter Test
9s
Linter Test
Unit Test
28s
Unit Test
Release Docs
0s
Release Docs
Fit to window
Zoom out
Zoom in

Annotations

1 error, 3 warnings, and 9 notices
Linter Test
Process completed with exit code 1.
Virtual Environment
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Linter Test
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Unit Test
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Unit Test
Starting action
Unit Test
HTTP Request: GET https://api.github.com/repos/jabardigitalservice/DataSae "HTTP/1.1 200 OK"
Unit Test
Generating comment for PR
Unit Test
HTTP Request: GET https://api.github.com/repos/jabardigitalservice/DataSae/contents/data.json?ref=python-coverage-comment-action-data "HTTP/1.1 200 OK"
Unit Test
HTTP Request: GET https://api.github.com/repos/jabardigitalservice/DataSae/pulls?state=open&head=jabardigitalservice%3Afeature%2Fdata_profiling&sort=updated&direction=desc "HTTP/1.1 200 OK"
Unit Test
No open PR found for branch feature/data_profiling, defaulting to all PRs
Unit Test
HTTP Request: GET https://api.github.com/repos/jabardigitalservice/DataSae/pulls?state=all&head=jabardigitalservice%3Afeature%2Fdata_profiling&sort=updated&direction=desc "HTTP/1.1 200 OK"
Unit Test
Cannot post comment. This is probably because this is an external PR, so it's expected. Ensure you have an additional `workflow_run` step configured as explained in the documentation (or alternatively, give up on PR comments for external PRs).
Unit Test
Ending action