Skip to content
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

Testing bazel-based build breakage with upstream rules_rust #485

Closed
wants to merge 5 commits into from

Conversation

dfreese
Copy link
Collaborator

@dfreese dfreese commented May 6, 2022

No description provided.

@dfreese dfreese marked this pull request as draft May 6, 2022 13:03
@dfreese
Copy link
Collaborator Author

dfreese commented May 6, 2022

@UebelAndre, in attempting to track down some of the errors in #482, it looks like cargo no longer gets pulled in automatically after bumping the version of rules_rust. I'm assuming that was an intentional change upstream. Before I splunk too much further, is the appropriate fix on that obvious to you?

@dfreese
Copy link
Collaborator Author

dfreese commented May 29, 2022

Looks like the breaking change was bazelbuild/rules_rust#1079, which flipped incompatible_disable_custom_test_launcher.

@dfreese dfreese changed the title insignificant change Testing bazel-based build breakage with upstream rules_rust May 29, 2022
@UebelAndre
Copy link
Collaborator

I'm so sorry, I don't know how I missed this issue! I think all that's needed is for the tests to explicitly handle making the CARGO and RUSTC environment variables absolute paths. Then I think all should be fine.

@dfreese
Copy link
Collaborator Author

dfreese commented Jun 18, 2022

fixed with #506, Thanks @sayrer

@dfreese dfreese closed this Jun 18, 2022
@dfreese dfreese deleted the lint branch June 18, 2022 23:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants