buildkite-config
PublicThis pipeline is intended for running rails/buildkite-config in CI
There were 8 test failures:
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 //v60:repos_3_test //v54:repos_3_test //v60:repos_0_test //v90:repos_0_test //v90:repos_3_test //v61:repos_3_test //v54:repos_0_test //v61:repos_0_test
💡 Check the Artifacts tab in the Test - e2e/pnpm_lockfiles step for logs from failed test targets.
Test - e2e/pnpm_lockfiles step for logs from failed test targets.There was 1 test failure:
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 Test - e2e/npm_translate_lock_replace_packages step for logs from failed test target.
Test - e2e/npm_translate_lock_replace_packages step for logs from failed test target.There was 1 test failure:
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 Test - e2e/gyp_no_install_script step for logs from failed test target.
Test - e2e/gyp_no_install_script step for logs from failed test target.
@@[unknown repo 'vendored_node_linux_amd64' requested from @@]//:bin/node failed during analysis
Test - e2e/vendored_nodeno 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/migrationRun the following command to try to reproduce locally:
bazel build --nobuild @@[unknown repo 'vendored_node_linux_amd64' requested from @@]//:bin/node
@@[unknown repo 'vendored_node_darwin_amd64' requested from @@]//:bin/node failed during analysis
Test - e2e/vendored_nodeno 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/migrationRun 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_windows_amd64' requested from @@]//:node.exe failed during analysis
Test - e2e/vendored_nodeno 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/migrationRun the following command to try to reproduce locally:
bazel build --nobuild @@[unknown repo 'vendored_node_windows_amd64' requested from @@]//:node.exe
@@[unknown repo 'repo' requested from @@]//:sources failed during analysis
Test - e2e/js_image_ocino 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/migrationRun 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
Test - e2e/js_image_ocino 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/migrationRun 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
Test - e2e/js_image_ocino 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/migrationRun the following command to try to reproduce locally:
bazel build --nobuild @@[unknown repo 'repo' requested from @@]//:dir
@@[unknown repo 'com_google_googleapis' requested from @@]//google/cloud/speech/v1p1beta1:speech_proto failed during analysis
Test - e2e/js_image_ocino such package '@@[unknown repo 'com_google_googleapis' requested from @@]//google/cloud/speech/v1p1beta1': The repository '@@[unknown repo 'com_google_googleapis' requested from @@]' could not be resolved: No repository visible as '@com_google_googleapis' 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/migrationRun the following command to try to reproduce locally:
bazel build --nobuild @@[unknown repo 'com_google_googleapis' requested from @@]//google/cloud/speech/v1p1beta1:speech_proto💅 buildkite-config: lintgit config --global --add safe.directory /workdir && bundle install && bundle exec rubocop
Waited 12m 22s
Ran in 45s
🧪 buildkite-config: rake testgit config --global --add safe.directory /workdir && bundle install && bundle exec rake test
Waited 12m 23s
Ran in 42s
✍️ buildkite-config: annotate diffmkdir -p tmp && sh -c "$ANNOTATE_COMMAND" > tmp/annotate.diff && if [[ -z $(grep '[^[:space:]]' tmp/annotate.diff) ]]; then && echo "annotate.diff is empty" && else && echo "annotate.diff is not empty" && cat tmp/annotate.diff && printf '%b\n' "$(cat tmp/annotate.diff)" | buildkite-agent annotate --style info --context config && fi
Waited 12m 24s
Ran in 46s
✍️ buildkite-config: annotate nightly diffmkdir -p tmp && sh -c "$ANNOTATE_COMMAND" > tmp/annotate-nightly.diff && if [[ -z $(grep '[^[:space:]]' tmp/annotate-nightly.diff) ]]; then && echo "annotate-nightly.diff is empty" && else && echo "annotate-nightly.diff is not empty" && cat tmp/annotate-nightly.diff && printf '%b\n' "$(cat tmp/annotate-nightly.diff)" | buildkite-agent annotate --style info --context nightly && fi
Waited 12m 33s
Ran in 46s
Build Rails main with new configTriggered build of main / HEAD on rails-ci Build Rails 6-1-stable with new configTriggered build of 6-1-stable / HEAD on rails-ci Build Rails main with new nightly configTriggered build of main / HEAD on Rails CI Nightly Build Rails 6-1-stable with new nightly configTriggered build of 6-1-stable / HEAD on Rails CI NightlyTotal Job Run Time: 2m 59s