There were 8 test failures:

//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
Test - e2e/pnpm_lockfiles step for logs from failed test targets.

There was 1 test failure:

//: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.

There was 1 test failure:

//: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.

There are currently 5 tests failing:

//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
Test step for logs from failing test targets.

@@[unknown repo 'vendored_node_windows_amd64' requested from @@]//:node.exe failed during analysis

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

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

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

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

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

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

Waited 3s
Ran in 9s
Total Job Run Time: 11s