-
-
Notifications
You must be signed in to change notification settings - Fork 681
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
reproducibility_test hardcodes the "host" output dir #2967
Comments
Thanks for the heads up. It seems that output paths are no longer predictable. Is there a recommendation for how to access the build artifact? |
Does |
You can save the build event messages and check them: https://docs.bazel.build/versions/main/build-event-protocol.html |
robfig
added a commit
that referenced
this issue
Dec 8, 2021
This allows us to find it at a known path. It is no longer possible to access genfiles at a known path: bazelbuild/bazel#14049 Fixes #2967 Fixes #3024
robfig
added a commit
that referenced
this issue
Dec 8, 2021
This allows us to find it at a known path. It is no longer possible to access genfiles at a known path: bazelbuild/bazel#14049 Fixes #2967 Fixes #3024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Testing rules_go against bazelbuild/bazel#14049 (which enables the toolchain transition globally), there is a failure in reproducibility_test (https://storage.googleapis.com/bazel-untrusted-buildkite-artifacts/ee4684ae-24f9-48bc-b094-0fa33588180e/tests/integration/reproducibility/reproducibility_test/attempt_1.log):
The cause of the error seems to be the hard-coded "host" in the output path. When this change reaches Bazel head, the test will begin failing until this can be fixed.
The text was updated successfully, but these errors were encountered: