-
Notifications
You must be signed in to change notification settings - Fork 272
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
Rules_apple fails on Bazel@HEAD in downstream CI. #1956
Comments
Seeing the same error on rules_swift |
Probably caused by bazelbuild/bazel@37b8e1b, /cc @keith |
Maybe https://github.com/bazel-contrib/bazel_features can help if you want to detect if this feature was removed or not. |
FYI @lberki @oquenchil |
blocked on bazelbuild/bazel#18321 |
Merged
After this is fixed, can you please also help address bazelbuild/examples#288 ? |
keith
added a commit
that referenced
this issue
May 5, 2023
Now that Xcode 14.1 is the minimum supported to the App Store, and Xcode 14.0 dropped support for bitcode, we don't need to handle these flags anymore. Closes #1956
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/2997#0187e486-336b-4f41-9a92-f6c60a3ce01d
Platform : rules_apple (Latest Bazel on :mac: (OpenJDK 11, Xcode))
Logs:
Culprit : https://buildkite.com/bazel/culprit-finder/builds/5478#0187e628-15b5-4551-a37f-4229dfbd5afb
Steps Followed:
CC @meteorcloudy
The text was updated successfully, but these errors were encountered: