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

Fix test target on macOS with Bazel@HEAD #558

Merged
merged 2 commits into from
Jan 26, 2021

Conversation

meteorcloudy
Copy link
Member

Avoid build artifacts name conflict after supports_dynamic_linker feature was removed from cc toolchain for macOS
Context: bazelbuild/bazel#4341 (comment)

@meteorcloudy
Copy link
Member Author

/cc @UebelAndre Can you take a look, this helps fix downstream breakage with Bazel@HEAD

Copy link
Collaborator

@UebelAndre UebelAndre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You will also need to remove the section from .bazelrc/presubmit.yaml disabling these tests on MacOS so we can confirm the changes actually fixed the issue:

- "-@examples//ffi/rust_calling_c:matrix_dylib_test"
- "-@examples//ffi/rust_calling_c:matrix_dynamically_linked"
- "-@examples//ffi/rust_calling_c/simple/..."

When I build locally on your branch, I run into the following error

ERROR: /private/var/tmp/_bazel_user/4affd8360c36081ca80c76cb4d709ed4/external/local_libstdcpp/BUILD.bazel:3:11: SolibSymlink _solib_darwin_x86_64/_U@local_Ulibstdcpp_S_S_Clibstdc++___U/libstdc++.6.dylib failed: missing input file 'external/local_libstdcpp/libstdc++.6.dylib', owner: '@local_libstdcpp//:libstdc++.6.dylib'
ERROR: /private/var/tmp/_bazel_user/4affd8360c36081ca80c76cb4d709ed4/external/local_libstdcpp/BUILD.bazel:3:11 SolibSymlink _solib_darwin_x86_64/_U@local_Ulibstdcpp_S_S_Clibstdc++___U/libstdc++.6.dylib failed: 1 input file(s) do not exist

I'm wondering if CI will show the same.

But super thanks for attempting to tackle this issue! I'd love to see all tests working 😄

@@ -20,9 +20,9 @@ cc_test(

## Do the same as above, but with a dynamic c library.

cc_library(
cc_import(
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you also update the load statement to include cc_import?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

@UebelAndre
Copy link
Collaborator

Also wondering if #226 is related to this

@meteorcloudy
Copy link
Member Author

#226 seems to be a different issue as this change was only made recently: bazelbuild/bazel@ec55533

@meteorcloudy
Copy link
Member Author

@UebelAndre I think those tests are disabled for other issues this PR isn't aimed to fix.
Even with those tests disabled, bazel build step still failed on Bazel CI due to a conflict of artifact names:
https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/1870#9d520a08-5923-414d-b7d0-6b253eb959dd
, which is what I want to fix to make our CI green again.

@illicitonion illicitonion merged commit de4a350 into bazelbuild:master Jan 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants