Skip to content
Examples

Fix websocket connection isn't properly closed #80

Sign in to view logs

Fix websocket connection isn't properly closed

Fix websocket connection isn't properly closed #80

Triggered via pull request November 21, 2023 10:48
@NicorettiNicoretti
synchronize #109
bug/#108-websocket-connection-isnt-properly-closed
Status Failure
Total duration 15m 28s
Artifacts –

examples.yml

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

Annotations

3 errors and 3 warnings
Build with Python 3.11 and Exasol latest-7.1
The operation was canceled.
Build with Python 3.11 and Exasol latest-7.0
The operation was canceled.
Build with Python 3.7 and Exasol latest-6.2
The operation was canceled.
Build with Python 3.11 and Exasol latest-7.1
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build with Python 3.11 and Exasol latest-7.0
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build with Python 3.7 and Exasol latest-6.2
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/