Skip to content
Build

[client-v2, jdbc-v2] Lazy String instantiation, Read bytes to buffer first #3653

Sign in to view logs

[client-v2, jdbc-v2] Lazy String instantiation, Read bytes to buffer first

[client-v2, jdbc-v2] Lazy String instantiation, Read bytes to buffer first #3653

Re-run triggered April 9, 2026 22:55
@chernserchernser
#2813
03/31/26/store_string_as_buffer
Status Failure
Total duration 9m 17s
Artifacts 5

build.yml

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

Annotations

3 errors and 4 warnings
JDBC driver + CH 25.8 (apache_http_client)
Process completed with exit code 1.
JDBC driver + CH 25.3 (apache_http_client)
Process completed with exit code 1.
JDBC driver + CH latest (apache_http_client)
Process completed with exit code 1.
Java client ( client-v2 ) + CH latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
JDBC driver + CH 25.8 (apache_http_client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
JDBC driver + CH 25.3 (apache_http_client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
JDBC driver + CH latest (apache_http_client)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
result test-jdbc-driver__25.3
907 KB
sha256:71d98c99e7a076eb8eca609f02e0f7ec7d3b74836be900580dc2f4509bb35ed0
result test-jdbc-driver__25.8
907 KB
sha256:9b21ff6f06752ff9820946228cc49119dd6ba209619fab44629b2c7211a92c02
result test-jdbc-driver__latest
910 KB
sha256:43da706a9d70305e65ac6cc6cdb57c8d4f65d8e36096af7e53a36091f37fe15a