Skip to content

write to js console why we need to reload #2298

write to js console why we need to reload

write to js console why we need to reload #2298

Re-run triggered July 31, 2023 11:56
Status Failure
Total duration 40m 39s
Artifacts 1

test.yml

on: push
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 3 warnings
test (3.8)
The job running on runner GitHub Actions 2 has exceeded the maximum execution time of 40 minutes.
test (3.8): tests/test_page.py#L171
some exception
test (3.8): tests/test_page.py#L171
some exception
test (3.8): tests/test_page.py#L171
some exception
test (3.8): tests/test_page.py#L171
some exception
test (3.8)
The operation was canceled.
test (3.9)
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/
test (3.11)
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/
test (3.10)
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
pytest-screenshots Expired
2.02 MB