-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
bazel: 7.0.2 -> 7.1.0 #295615
bazel: 7.0.2 -> 7.1.0 #295615
Conversation
@layus I don't remember what the process is for updating |
I enter the environment with nix-shell -A and run the process manually to update the lockfile then copy that new version. Nothing much smarter sadly.
IMO we should use better projects for tests. These examples are not updated very frequently.
Le 13 mars 2024 15:18:05 GMT+01:00, Noah S-C ***@***.***> a écrit :
…
@layus I don't remember what the process is for updating `cpp-test-MODULE.bazel.lock` and I cant find instructions on it.
--
Reply to this email directly or view it on GitHub:
#295615 (comment)
You are receiving this because you were mentioned.
Message ID: ***@***.***>
|
Not sure if I did it right, presumably not as
|
OfBorg seems happy with the tests, even though I couldnt get them to be successful locally 🤷 marked as ready for review https://github.com/NixOS/nixpkgs/pull/295615/checks?check_run_id=22622593892 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was able to build and run Bazel 7.1 on some real targets already up to date with 7.0.2.
I did have a different failure locally with the tests having to do with failed fetches from the bzlmod central registry. I ran it a few days ago, but I can rerun it to find the error message, or perhaps it is expected. I did not run the tests locally with the 7.0.2 upgrade, so I don't know that this PR is the culprit.
Well, it failed for x86 and arm64 darwin... I don't know if we should care about that? From a quick glance, the changes look good. Thanks! |
Using my fork with open PR: NixOS/nixpkgs#295615 Im needing 7.1 sooner than later, given its new features and this repo also using 7.1 (so all new features are fair game for it!) Cached version is pushed to sourcegraph-noah.cachix.org, which I've added at the top here so you too can avoid building it locally 🙂 ## Test plan Tested locally 😎
|
7.1.1 changed the format of MODULE.bazel.lock in a way thatd require a lot more work in https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/tools/build-managers/bazel/bazel_7/bazel-repository-cache.nix, unless we want to take a hit in closure size by fetching everything instead of only a subset that this function does. |
Do you think that we should try to get 7.1 merged first and then work on 7.1.1 after? |
I think this is best for now. |
Could we merge this? There was a critical level CVE in rust https://blog.rust-lang.org/2024/04/09/cve-2024-24576.html and the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested this on some fairly large repositories on Linux x86_64
fwiw I don't have merge permissions for this. Just a lowly contributor |
@aaronmondal bazelbuild/rules_rust#2612 will fix rules_rust requiring Bazel 7.1 |
Description of changes
Changelog: https://github.com/bazelbuild/bazel/releases/tag/7.1.0
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.