Conversation
… another workspace. Signed-off-by: Steffen Smolka <steffen.smolka@gmail.com>
Member
Author
|
Jackpot! |
smolkaj
added a commit
that referenced
this pull request
Feb 20, 2026
…her Bazel workspace. Details: - In Bazel, it is possible and not uncommon that a project builds from its own workspace, but fails to build when depended on from another workspace. - We have an example project in example/using-bzlmod that we build in our CI script to ensure both direct and transitive builds work. - Despite this, in bazelbuild/bazel-central-registry#7594, P4Runtime did not build even though our CI script passed. - The gap: our example project exercises some, but not all @p4runtime targets in a transitive fashion. - The solution: run bazel build @p4runtime//... from the example workspace to close the gap. - The proof: I reproduced the issue seen in bazelbuild/bazel-central-registry#7594 in #591. Signed-off-by: Steffen Smolka <steffen.smolka@gmail.com>
smolkaj
added a commit
that referenced
this pull request
Feb 20, 2026
…her Bazel workspace. Details: - In Bazel, it is possible and not uncommon that a project builds from its own workspace, but fails to build when depended on from another workspace. - We have an example project in example/using-bzlmod that we build in our CI script to ensure both direct and transitive builds work. - Despite this, in bazelbuild/bazel-central-registry#7594, P4Runtime did not build even though our CI script passed. - The gap: our example project exercises some, but not all @p4runtime targets in a transitive fashion. - The solution: run bazel build @p4runtime//... from the example workspace to close the gap. - The proof: I reproduced the issue seen in bazelbuild/bazel-central-registry#7594 in #591. Signed-off-by: Steffen Smolka <steffen.smolka@gmail.com>
smolkaj
added a commit
that referenced
this pull request
Feb 20, 2026
…her Bazel workspace. Details: - In Bazel, it is possible and not uncommon that a project builds from its own workspace, but fails to build when depended on from another workspace. - We have an example project in example/using-bzlmod that we build in our CI script to ensure both direct and transitive builds work. - Despite this, in bazelbuild/bazel-central-registry#7594, P4Runtime did not build even though our CI script passed. - The gap: our example project exercises some, but not all @p4runtime targets in a transitive fashion. - The solution: run bazel build @p4runtime//... from the example workspace to close the gap. - The proof: I reproduced the issue seen in bazelbuild/bazel-central-registry#7594 in #591. Signed-off-by: Steffen Smolka <steffen.smolka@gmail.com>
smolkaj
added a commit
that referenced
this pull request
Feb 20, 2026
…her Bazel workspace. Details: - In Bazel, it is possible and not uncommon that a project builds from its own workspace, but fails to build when depended on from another workspace. - We have an example project in example/using-bzlmod that we build in our CI script to ensure both direct and transitive builds work. - Despite this, in bazelbuild/bazel-central-registry#7594, P4Runtime did not build even though our CI script passed. - The gap: our example project exercises some, but not all @p4runtime targets in a transitive fashion. - The solution: run bazel build @p4runtime//... from the example workspace to close the gap. - The proof: I reproduced the issue seen in bazelbuild/bazel-central-registry#7594 in #591. Signed-off-by: Steffen Smolka <steffen.smolka@gmail.com>
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
1 participant
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.
In bazelbuild/bazel-central-registry#7594, P4Runtime did not build correctly even though we have CI set up to ensure that it does.
Here is what I believe is going on:
example/using-bzlmodthat we build in our CI script to ensure both direct and transitive builds work.@p4runtimetargets in a transitive fashion.bazel build @p4runtime//...from the example workspace to close the gap.If my theory is correct, the CI run on this PR should fail and reproduce the issue I encountered in bazelbuild/bazel-central-registry#7594.