enterprise-search-ruby

Public

Enterprise Search Ruby Client

[CI] Adds Ruby 3.4 to unit tests in GH Actions

#564
/
main/a4947fa
Passed in 11m 43s
:pipeline:🌱 Upload Initial Pipeline Steps
:elastic-enterprise-search: Enterprise Search :rspec: API Integration Tests :ruby: v3.4
:elastic-enterprise-search: Enterprise Search :rspec: API Integration Tests :ruby: v3.3
:elastic-enterprise-search: Enterprise Search :rspec: API Integration Tests :ruby: v3.2
:elastic-enterprise-search: Enterprise Search :rspec: API Integration Tests :ruby: v3.1
Log Results
Fernando Briano
Fernando Briano
Created
Triggered from Webhook
There were 8 test failures:
:bazel: Test - e2e/pnpm_lockfiles
//v54:repos_0_test failed
//v54:repos_3_test failed
//v60:repos_0_test failed
//v60:repos_3_test failed
//v61:repos_0_test failed
//v61:repos_3_test failed
//v90:repos_0_test failed
//v90:repos_3_test failed
Run the following command to try to reproduce locally:
bazel test //v90:repos_0_test //v60:repos_0_test //v61:repos_3_test //v90:repos_3_test //v54:repos_3_test //v61:repos_0_test //v60:repos_3_test //v54:repos_0_test
💡 Check the Artifacts tab in the :bazel: Test - e2e/pnpm_lockfiles step for logs from failed test targets.
There was 1 test failure:
:bazel: Test - e2e/npm_translate_lock_replace_packages
//:write_npm_translate_lock_bzlmod_test failed
Run the following command to try to reproduce locally:
bazel test //:write_npm_translate_lock_bzlmod_test
💡 Check the Artifacts tab in the :bazel: Test - e2e/npm_translate_lock_replace_packages step for logs from failed test target.
There was 1 test failure:
:bazel: Test - e2e/gyp_no_install_script
//:write_npm_translate_lock_bzlmod_test failed
Run the following command to try to reproduce locally:
bazel test //:write_npm_translate_lock_bzlmod_test
💡 Check the Artifacts tab in the :bazel: Test - e2e/gyp_no_install_script step for logs from failed test target.
There are currently 5 tests failing:
:bazel: Test
//js/private/test:write_launcher_bzlmod_test failed
//npm/private/test:write_npm_translate_lock_bzlmod_0_test failed
//npm/private/test:write_npm_translate_lock_bzlmod_1_test failed
//npm/private/test:write_npm_translate_lock_bzlmod_2_test failed
//npm/private/test:write_npm_translate_lock_bzlmod_3_test failed
Run the following command to try to reproduce locally:
bazel test //npm/private/test:write_npm_translate_lock_bzlmod_0_test //js/private/test:write_launcher_bzlmod_test //npm/private/test:write_npm_translate_lock_bzlmod_3_test //npm/private/test:write_npm_translate_lock_bzlmod_2_test //npm/private/test:write_npm_translate_lock_bzlmod_1_test
💡 Check the Artifacts tab in the :bazel: Test step for logs from failing test targets.
@@[unknown repo 'vendored_node_windows_amd64' requested from @@]//:node.exe failed during analysis
:bazel: Test - e2e/vendored_node
no such package '@@[unknown repo 'vendored_node_windows_amd64' requested from @@]//': The repository '@@[unknown repo 'vendored_node_windows_amd64' requested from @@]' could not be resolved: No repository visible as '@vendored_node_windows_amd64' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration
Run the following command to try to reproduce locally:
bazel build --nobuild @@[unknown repo 'vendored_node_windows_amd64' requested from @@]//:node.exe
@@[unknown repo 'vendored_node_darwin_amd64' requested from @@]//:bin/node failed during analysis
:bazel: Test - e2e/vendored_node
no such package '@@[unknown repo 'vendored_node_darwin_amd64' requested from @@]//': The repository '@@[unknown repo 'vendored_node_darwin_amd64' requested from @@]' could not be resolved: No repository visible as '@vendored_node_darwin_amd64' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration
Run the following command to try to reproduce locally:
bazel build --nobuild @@[unknown repo 'vendored_node_darwin_amd64' requested from @@]//:bin/node
@@[unknown repo 'vendored_node_linux_amd64' requested from @@]//:bin/node failed during analysis
:bazel: Test - e2e/vendored_node
no such package '@@[unknown repo 'vendored_node_linux_amd64' requested from @@]//': The repository '@@[unknown repo 'vendored_node_linux_amd64' requested from @@]' could not be resolved: No repository visible as '@vendored_node_linux_amd64' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration
Run the following command to try to reproduce locally:
bazel build --nobuild @@[unknown repo 'vendored_node_linux_amd64' requested from @@]//:bin/node
@@[unknown repo 'repo' requested from @@]//:sources failed during analysis
:bazel: Test - e2e/js_image_oci
no such package '@@[unknown repo 'repo' requested from @@]//': The repository '@@[unknown repo 'repo' requested from @@]' could not be resolved: No repository visible as '@repo' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration
Run the following command to try to reproduce locally:
bazel build --nobuild @@[unknown repo 'repo' requested from @@]//:sources
@@[unknown repo 'repo' requested from @@]//:source_txt failed during analysis
:bazel: Test - e2e/js_image_oci
no such package '@@[unknown repo 'repo' requested from @@]//': The repository '@@[unknown repo 'repo' requested from @@]' could not be resolved: No repository visible as '@repo' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration
Run the following command to try to reproduce locally:
bazel build --nobuild @@[unknown repo 'repo' requested from @@]//:source_txt
@@[unknown repo 'repo' requested from @@]//:dir failed during analysis
:bazel: Test - e2e/js_image_oci
no such package '@@[unknown repo 'repo' requested from @@]//': The repository '@@[unknown repo 'repo' requested from @@]' could not be resolved: No repository visible as '@repo' from main repository. Was the repository introduced in WORKSPACE? The WORKSPACE file is disabled by default in Bazel 8 (late 2024) and will be removed in Bazel 9 (late 2025), please migrate to Bzlmod. See https://bazel.build/external/migration
Run the following command to try to reproduce locally:
bazel build --nobuild @@[unknown repo 'repo' requested from @@]//:dir
:pipeline:🌱 Upload Initial Pipeline Stepsbuildkite-agent pipeline upload
Waited 28s
·
Ran in 4s
Agent
Matrix
:elastic-enterprise-search: Enterprise Search :rspec: API Integration Tests :ruby: v3.4./.buildkite/run-tests.sh
Waited 1m 7s
·
Ran in 9m 31s
Agent
Matrix
:elastic-enterprise-search: Enterprise Search :rspec: API Integration Tests :ruby: v3.3./.buildkite/run-tests.sh
Waited 1m 3s
·
Ran in 9m 13s
Agent
Matrix
:elastic-enterprise-search: Enterprise Search :rspec: API Integration Tests :ruby: v3.2./.buildkite/run-tests.sh
Waited 1m 13s
·
Ran in 9m 6s
Agent
Matrix
:elastic-enterprise-search: Enterprise Search :rspec: API Integration Tests :ruby: v3.1./.buildkite/run-tests.sh
Waited 1m 13s
·
Ran in 9m 35s
Agent
Build will continue even if previous stage fails
Log Results./.buildkite/log-results.sh
Waited 49s
·
Ran in 3s
Agent
Total Job Run Time: 37m 31s