-
Notifications
You must be signed in to change notification settings - Fork 440
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
Updated Bazelmod cross compilation to catch MacOS sys dependency issues #2926
Conversation
Signed-off-by: Marvin Hansen <marvin.hansen@gmail.com>
Signed-off-by: Marvin Hansen <marvin.hansen@gmail.com>
Signed-off-by: Marvin Hansen <marvin.hansen@gmail.com>
Signed-off-by: Marvin Hansen <marvin.hansen@gmail.com>
Signed-off-by: Marvin Hansen <marvin.hansen@gmail.com>
Signed-off-by: Marvin Hansen <marvin.hansen@gmail.com>
Signed-off-by: Marvin Hansen <marvin.hansen@gmail.com>
Signed-off-by: Marvin Hansen <marvin.hansen@gmail.com>
Signed-off-by: Marvin Hansen <marvin.hansen@gmail.com>
Update:
However, I am not familiar with BazelCI, but is there a way to add a single MacOS runner that basically runs all Bazelmod tests similar to the crate universe runner for the Workspace examples? Would be great if someone with a solid understanding of the CI would ensure that all Bazelmod examples get build and tested on MacOS. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some comments. Stuff looks largely reasonable, (note unfortunately I'm not really familiar with the bzlmod presubmits).
.bazelci/presubmit.yml
Outdated
platform: ubuntu2004 | ||
working_directory: examples/bzlmod/proto_with_toolchain | ||
build_targets: | ||
- "//..." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this removal intentional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, that was an accident. Probably a cut instead of copy.
Good catch. Thanks for point it out.
Resolves: bazelbuild#2926 (comment) Signed-off-by: Marvin Hansen <marvin.hansen@gmail.com>
Resolves: bazelbuild#2926 (comment) Signed-off-by: Marvin Hansen <marvin.hansen@gmail.com>
Resolves: bazelbuild#2926 (comment) Signed-off-by: Marvin Hansen <marvin.hansen@gmail.com>
@krasimirgg I addresses all of your issues with the latest commits. Please review again. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
In general having a macos CI sounds reasonable.
As discussed in issue #2917,
this updated cross compilation example serves as a bridge until the exact cause of the sys crates not building on Mac issue has been found and better regression testing has been added.
Also, I took the freedom to trim and streamline the LLVM setup making it easier to configure while preserving the property that it caches failing sys crate builds. Updated the Readme accordingly.