-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build failure: bazel-watcher #253706
Comments
Several errors like this locally and in https://hydra.nixos.org/build/245701308/nixlog/7:
|
On the same system, with bazelisk, |
merge 8c7c922/#231839 introduced a build failure (found via git bisect) which merged this change: Reverting it on master makes it work but
Maybe divanorama can help out fixing it... |
@divanorama :) |
The |
I was wrong. The fetchAttrs.sha256 hid that it was, in fact, broken before 8c7c922/https://github.com/NixOS/nixpkgs/pull/231839 $ git checkout 8c7c922^
$ nix build -L .#bazel-watcher # works diff --git a/pkgs/development/tools/bazel-watcher/default.nix b/pkgs/development/tools/bazel-watcher/default.nix
index 137e54b04c33..75a7d76a59db 100644
--- a/pkgs/development/tools/bazel-watcher/default.nix
+++ b/pkgs/development/tools/bazel-watcher/default.nix
@@ -82,7 +82,7 @@ buildBazelPackage rec {
rm -rf $bazelOut/external/com_google_protobuf
'';
- sha256 = "sha256-lC9e5Z2cxLAeWXkiFGmcB6aOaurMvwrP/k5jl3gCfAc=";
+ sha256 = "";
};
buildAttrs = { $ nix build -L .#bazel-watcher # DOES NOT work anymore |
I bisected this to the following commit: 1bb67a9 with this bisect script:
Unfortunately, it is a huge merge. |
Okay fetching broke when go was unpinned: dc6ea0a |
Maybe related to golang/go#61928 |
Steps To Reproduce
Steps to reproduce the behavior:
nix-build -A bazel-watcher
Build log
https://gist.github.com/kyleconroy/ff7de358868ddc33e4803392c8f947d4
Additional context
The builds are also failing on Hydra
Notify maintainers
@kalbasit
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.The text was updated successfully, but these errors were encountered: