Skip to content

events: dynamic and statically added events should appear differently #54

events: dynamic and statically added events should appear differently

events: dynamic and statically added events should appear differently #54

Triggered via pull request December 7, 2023 12:04
Status Failure
Total duration 59s
Artifacts

test_pull_requests.yml

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

Annotations

5 errors and 4 warnings
build (3.11)
Process completed with exit code 1.
build (3.8)
The job was canceled because "_3_11" failed.
build (3.8)
Process completed with exit code 1.
build (3.9)
Process completed with exit code 1.
build (3.10)
The operation was canceled.
build (3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (3.10)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/