Repository navigation
chore(release): 1.14.0 #37
socket-release-bot[bot]bazel-windows.yml
on: pull_request
Maven on Windows x64
10m 19s
Annotations
2 errors
|
Maven on Windows x64
Process completed with exit code 1.
|
|
src/commands/manifest/bazel/bazel-native.e2e.test.mts > native Bazel Maven extraction > runs the packaged CLI in workspace mode:
src/commands/manifest/bazel/bazel-native.e2e.test.mts#L147
Error: command failed
❯ promiseSpawn node_modules/.pnpm/@SocketSecurity+registry@1._22f3765a396f8b31ee26f9d22e305406/node_modules/@socketsecurity/registry/external/@npmcli/promise-spawn.js:498:24
❯ spawn node_modules/.pnpm/@SocketSecurity+registry@1._22f3765a396f8b31ee26f9d22e305406/node_modules/@socketsecurity/registry/lib/spawn.js:162:22
❯ src/commands/manifest/bazel/bazel-native.e2e.test.mts:147:30
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { cmd: 'D:\a\_temp\bazel-tools\node\node-v24.14.1-win-x64\node.exe', args: [ 'D:\a\_temp\bazel-installation/node_modules/socket/bin/cli.js', 'manifest', 'bazel', '--bazel', 'D:\a\_temp\bazel-tools\bin\bazelisk.EXE', '--out', 'C:\Users\RUNNER~1\AppData\Local\Temp\bazel native an1Jn9\packaged output', 'C:\Users\RUNNER~1\AppData\Local\Temp\bazel native an1Jn9\packaged project' ], code: 1, signal: null, stdout: 'bazel2maven:', stderr: 'CLI: v1.14.0 | cmd: socket manifest bazel | org: (not set) | token: (not set)\n\n i - src dir: `C:\Users\RUNNER~1\AppData\Local\Temp\bazel native an1Jn9\packaged project`\n i - out dir: `C:\Users\RUNNER~1\AppData\Local\Temp\bazel native an1Jn9\packaged output`\ni Using bazel: D:\a\_temp\bazel-tools\bin\bazelisk.EXE\ni Workspace .: bzlmod=false workspace=true\ni Workspace .: discovered 0 Maven repo(s): (none)\n\n\n× Invalid input: No supported Bazel ecosystems detected (maven, pypi). Ensure rules_jvm_external, rules_python pip_parse/pip_install/pip_repository, or pip.parse is configured.' }
|