Repository navigation
Add named executable tools to bashtest - #55
Merged
Merged
Conversation
helly25
added this pull request to stack #57
October 17, 2026 16:50
helly25
removed this pull request from stack #57
October 17, 2026 16:53
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add
tools = {"GENERATOR": "//tools:generator"}to build helper executables for the platform running a test and export their resolved paths automatically. Scripts invoke"${GENERATOR}"; helper runfiles are included, including Windows executables and manifest-only layouts.AG;DR
main; dependency Support Windows Bash and manifest-only runfiles #54 has merged. Merge this PR before Provision Bash and Unix utilities automatically on Windows #56. The synchronization merge preserves the previously tested files exactly: Support Windows Bash and manifest-only runfiles #54 was squash-merged with an identical tree.config.exec("test"), preserving the test execution group's platform constraints. A non-testsh_binarytarget supplies the rules_shell launcher; a generated manifest maps environment names to executable runfiles. With tools there is exactly one test target, with no forced manual tag or private visibility on the launcher.data, helper default/data runfiles, inherited test environment, and coverage metadata. Multiple environment names can reference one executable. The test rule owns environment expansion, preserving runfiles-relative location paths on Bazel 7 and 9.dataandtools. Avoid mixing target- and execution-configured instances of the same generated runfile in transitive dependencies.bazel testandbazel run, and invalid declarations. The external consumer selects different ordinary and test execution platforms on Bazel 9; Bazel 7 uses its supportedexec_compatible_withattribute.tool_fixture.bzlis private test infrastructure, with private load visibility; it is not part of the public API.1ae692c: localbazel test //...(8 passing) and repository-wide pre-commit pass. All fresh PR CI checks againstmainpassed, including Linux, macOS, Windows, release-site checks, pre-commit, and the required done gate. Post-merge main CI for Support Windows Bash and manifest-only runfiles #54 also passed.