Smoke tests

Smoke tests #2695

Sign in to view logs

Triggered via push June 10, 2026 00:55

CLIENT-4836-add-string-ops-and-expressions

Status Failure

Total duration 11m 37s

Artifacts 7

smoke-tests.yml

on: push

generate-coverage-report

build-and-test-using-debug-interpreter

build / get-build-runner-os

test-sanitizer / get-build-runner-os

coverage-upload

Matrix: build / build-wheel

Matrix: test-sanitizer / build-wheel

Matrix: build / test-wheel

Waiting for pending jobs

Matrix: test-sanitizer / test-wheel

Matrix: test-metrics

test-ee / test-artifact

Matrix: stubtest-or-doctest

Matrix: test-ce

Matrix: test-full-suite

Matrix: test-user-agent

Annotations

11 errors, 25 warnings, and 1 notice

generate-coverage-report

Process completed with exit code 1.

generate-coverage-report

Process completed with exit code 2.

coverage-upload

Process completed with exit code 1.

test-ce (3.13) / test-artifact

Process completed with exit code 2.

build-and-test-using-debug-interpreter

Process completed with exit code 2.

test-ce (3.12) / test-artifact

Process completed with exit code 2.

test-ce (3.14) / test-artifact

Process completed with exit code 2.

test-ce (3.11) / test-artifact

Process completed with exit code 2.

test-ce (3.10) / test-artifact

Process completed with exit code 2.

test-full-suite (dont_validate_keys) / test-artifact

Process completed with exit code 2.

test-sanitizer / test-wheel (3.10) / test-artifact

Process completed with exit code 2.

build / build-wheel (3.13) / execute-build

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/setup-jfrog-cli@893a92f96c7727242adf0e603c77b1f2a22390e1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

build / build-wheel (3.14) / execute-build

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/setup-jfrog-cli@893a92f96c7727242adf0e603c77b1f2a22390e1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

build / build-wheel (3.12) / execute-build

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/setup-jfrog-cli@893a92f96c7727242adf0e603c77b1f2a22390e1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

build / build-wheel (3.11) / execute-build

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/setup-jfrog-cli@893a92f96c7727242adf0e603c77b1f2a22390e1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

build / build-wheel (3.10) / execute-build

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/setup-jfrog-cli@893a92f96c7727242adf0e603c77b1f2a22390e1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

test-sanitizer / build-wheel (3.10) / execute-build

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/setup-jfrog-cli@893a92f96c7727242adf0e603c77b1f2a22390e1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

generate-coverage-report

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

generate-coverage-report

Strong consistency directives must be present in your custom config; the action does not inject namespace SC settings into user-provided configs

test-ce (3.13) / test-artifact

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

build-and-test-using-debug-interpreter

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

build-and-test-using-debug-interpreter

Strong consistency directives must be present in your custom config; the action does not inject namespace SC settings into user-provided configs

test-ce (3.12) / test-artifact

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

test-ce (3.14) / test-artifact

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

test-user-agent (true my_app_id)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

test-ce (3.11) / test-artifact

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

test-user-agent (false)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

test-user-agent (true)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

test-ce (3.10) / test-artifact

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

stubtest-or-doctest (doctest)

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

test-full-suite (dont_validate_keys) / test-artifact

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

test-full-suite (dont_validate_keys) / test-artifact

Strong consistency directives must be present in your custom config; the action does not inject namespace SC settings into user-provided configs

test-sanitizer / test-wheel (3.10) / test-artifact

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

test-sanitizer / test-wheel (3.10) / test-artifact

Strong consistency directives must be present in your custom config; the action does not inject namespace SC settings into user-provided configs

test-ee / test-artifact

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/login-action@5e57cd118135c172c3672efd75eb46360885c0ef, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

test-ee / test-artifact

Strong consistency directives must be present in your custom config; the action does not inject namespace SC settings into user-provided configs

test-user-agent (false)

Ignoring features-file/features-content for Aerospike Server Community

Artifacts

Produced during runtime

Name	Size	Digest
build-artifacts-3.10-linux_x86_64 Expired	3.56 MB	`sha256:1af6987c2abf9950d10ff0360d88e02c0cc9f78642d519a418217d898ca3c9f1`
build-artifacts-3.10-linux_x86_64-sanitizer Expired	5.1 MB	`sha256:920cab09f2598eb40cffb82c1145a51c27b60e9f400d6dc7783d9c3cd3e59b44`
build-artifacts-3.11-linux_x86_64 Expired	3.58 MB	`sha256:af9960a638d04d8a843b123c1e10c9cfaa0cc55b555ecd080c5c3b446e4881fc`
build-artifacts-3.12-linux_x86_64 Expired	3.61 MB	`sha256:960c01c9ab905f0f970cb0d2c7c71490f4fda09266904857deb6ff94b133df1f`
build-artifacts-3.13-linux_x86_64 Expired	3.61 MB	`sha256:4d4559b7a73da57e9b88fccd540422fb798bfb3bd21561d7c1e0176aee2f3edc`
build-artifacts-3.14-linux_x86_64 Expired	3.6 MB	`sha256:a479c2d5ee77aa062137eeb81e93b81cc0a594b3e2d79b245ec2df73a24de0e3`
coverage-report	3.29 MB	`sha256:83ffd4bca559a6bf939317eb86d9f80c5dcc721fb59704aa24e697af3e526d85`