Skip to content

change connection schema after USE is executed #2376

change connection schema after USE is executed

change connection schema after USE is executed #2376

Re-run triggered February 12, 2025 08:32
Status Failure
Total duration 14m 11s
Artifacts 5

build.yml

on: pull_request
Compile (JDK 8)
4m 34s
Compile (JDK 8)
Test Native Image
3m 55s
Test Native Image
Matrix: test-java-client
Matrix: test-jdbc-driver
Matrix: test-multi-env
Matrix: test-r2dbc-driver
Matrix: test-with-cloud
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 1 warning
jdbc-v2 + CH cloud
Process completed with exit code 1.
client-v2 + CH cloud
Process completed with exit code 1.
clickhouse-jdbc + CH cloud
Process completed with exit code 1.
clickhouse-http-client + CH cloud
Process completed with exit code 1.
Java client ( client-v2 ) + CH 23.8
Process completed with exit code 1.
Test Native Image
This build uses the last update of Oracle GraalVM for JDK 17 under the GFTC. More details: https://github.com/marketplace/actions/github-action-for-graalvm#notes-on-oracle-graalvm-for-jdk-17

Artifacts

Produced during runtime
Name Size
result test-java-client_23.8
12.5 MB
result test-with-cloud_clickhouse-http-client_cloud
241 KB
result test-with-cloud_clickhouse-jdbc_cloud
237 KB
result test-with-cloud_client-v2_cloud
263 KB
result test-with-cloud_jdbc-v2_cloud
173 KB