rules_go: Gazelle fails on Windows
Error:
ERROR: Analysis of target '//:gazelle' failed; build aborted: no such package '@org_golang_x_tools//go/analysis': Traceback (most recent call last):
| File "C:/users/b/_bazel_b/vdpycznq/external/bazel_tools/tools/build_defs/repo/http.bzl", line 55
| patch(ctx)
| File "C:/users/b/_bazel_b/vdpycznq/external/bazel_tools/tools/build_defs/repo/utils.bzl", line 80, in patch
| fail(("Error applying patch %s:\n%s%s...)))
| Error applying patch @io_bazel_rules_go//third_party:org_golang_x_tools-gazelle.patch:
| /usr/bin/bash: patch: command not found
This is on Bazel CI (https://buildkite.com/bazel/rules-typescript-typescript/builds/749#928243ad-1996-4d93-972a-f8f5600100be), trying to test https://github.com/bazelbuild/rules_typescript/pull/308 (in order to update rules_typescript to rules_go 0.16.0).
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 25 (25 by maintainers)
Commits related to this issue
- Add MSYS2's /usr/bin to the Windows PATH Requested in https://github.com/bazelbuild/rules_go/issues/1775 — committed to bazelbuild/continuous-integration by philwo 6 years ago
- Add MSYS2's /usr/bin to the Windows PATH Requested in https://github.com/bazelbuild/rules_go/issues/1775 — committed to joeleba/continuous-integration by philwo 6 years ago
Creating a new Windows image now.
I don’t think we can currently do that, but I’ll prepare Windows images with MSYS2 on the PATH. Let’s see how that goes.