Skip to content

Course detail fetch from elasticsearch, add invitation_only field #17

Course detail fetch from elasticsearch, add invitation_only field

Course detail fetch from elasticsearch, add invitation_only field #17

Triggered via pull request October 19, 2023 12:22
Status Failure
Total duration 20m 25s
Artifacts 3

ci.yml

on: pull_request
Matrix: pytest
coverage
0s
coverage
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 3 warnings
quality
Process completed with exit code 2.
pytest (py38, django32, mysql57, 3)
Process completed with exit code 2.
pytest (py38, django32, mysql80, 1)
Process completed with exit code 2.
pytest (py38, django32, mysql57, 1)
Process completed with exit code 2.
pytest (py38, django32, mysql57, 5)
Process completed with exit code 2.
pytest (py38, django32, mysql80, 5)
Process completed with exit code 2.
pytest (py38, django32, mysql80, 3)
Process completed with exit code 2.
pytest (py38, django32, mysql57, 4)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
pytest (py38, django32, mysql57, 2)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
pytest (py38, django32, mysql57, 6)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Artifacts

Produced during runtime
Name Size
coverage2 Expired
1.55 MB
coverage4 Expired
1.72 MB
coverage6 Expired
1.54 MB