Skip to content

Allow to set connection options on a per server basis #168

Allow to set connection options on a per server basis

Allow to set connection options on a per server basis #168

Triggered via pull request August 7, 2024 06:45
Status Failure
Total duration 1m 5s
Artifacts

build.yml

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

Annotations

15 errors and 1 warning
test (3.3.0, 5)
Process completed with exit code 18.
test (3.3.0, 4)
The job was canceled because "_3_3_0_5" failed.
test (3.3.0, 4)
The operation was canceled.
test (3.2.3, 4)
The job was canceled because "_3_3_0_5" failed.
test (3.2.3, 4)
The operation was canceled.
test (3.2.3, 5)
The job was canceled because "_3_3_0_5" failed.
test (3.2.3, 5)
The operation was canceled.
test (3.1.4, 4)
The job was canceled because "_3_3_0_5" failed.
test (3.1.4, 4)
The operation was canceled.
test (3.1.4, 5)
The job was canceled because "_3_3_0_5" failed.
test (3.1.4, 5)
The operation was canceled.
test (3.0.6, 4)
The job was canceled because "_3_3_0_5" failed.
test (3.0.6, 4)
The operation was canceled.
test (3.0.6, 5)
The job was canceled because "_3_3_0_5" failed.
test (3.0.6, 5)
The operation was canceled.
test (3.3.0, 5)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/