Add gzip and gnutar to default bazel-bash tools.#54459
Add gzip and gnutar to default bazel-bash tools.#54459Profpatsch merged 2 commits intoNixOS:masterfrom
Conversation
|
LGTM |
|
I tried to exec |
|
I'm on NixOS, I'll give it a try. Any commands I should execute in the build to test it out? |
|
@ivegotasthma Good you ask, I added a test, also cleaned up the other test a bit. Could you take a look on the changes, as well try the local test command mentioned? I don't expect it to behave differently, but who knows. By the way, why are these tests in passthru? Are they executed by some integration tool? |
|
@robinp I'll tell you when I've tested it. I'm still building bazel. |
|
When I was building bazel I got: It happened multiple times, but it could be a local issue. I ran the tests with Tests pass fine, and it LGTM.
I'm not sure why they're there or how they're executed. Lets ask the people who wrote them. @NinjaTrappeur @Profpatsch |
See #44439 . To the best of my understanding (Profpatsch wrote the test), they are evaluated by ofborg ( #53988 (comment) ). |
|
@ivegotasthma thanks, the issue seems unrelated. @NinjaTrappeur thanks, will try that invocation! @GrahamcOfBorg build bazel.tests |
|
@GrahamcOfBorg build bazel.tests |
… by rules, mostly due to Bazel's one-output rule.
|
@Profpatsch gentle ping. |
No, not yet. The plan is to add some support to ofborg. But I haven’t had the time yet. @GrahamcOfBorg build bazel.tests ^ @robinp I think you need to be a member for that. |
|
Looking good, thanks! |
Motivation for this change
These are often used by rules, mostly due to Bazel's one-output restriction, where multi-output results are tarred up or archived in other way. Also, these are harmless tools to include.
Continuation of #50765.
Things done
sandboxinnix.confon non-NixOS)nix-shell -p nox --run "nox-review wip"./result/bin/)nix path-info -Sbefore and after)CC @Profpatsch