-
Notifications
You must be signed in to change notification settings - Fork 541
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
boto_test broken on mac #98
Comments
Ping? |
Still broken with Bazel 0.15: https://storage.googleapis.com/bazel-buildkite-artifacts/e71e36da-530e-47cf-a038-698c2d1999b6/examples/boto/boto_test/attempt_1.log
|
Still failing on Mac in https://buildkite.com/bazel/bazel-toolchains/builds/363. |
/cc @aragos |
This is still failing on Mac at HEAD. |
And still failing on macs: https://buildkite.com/bazel/bazel-with-downstream-projects-bazel/builds/386#aaf0f0e0-66a6-4167-b5ef-47be90bff33f cc @brandjon |
Any progress on this? |
Sounds like maybe on mac an old version of six is getting installed? Investigating... |
Confirmed that on mac six is 1.4.1 (the linked thread says it should be at least 1.5). On Ubuntu it's 1.10.0. |
Ah, this looks mighty suspicious: https://stackoverflow.com/questions/29485741/unable-to-upgrade-python-six-package-in-mac-osx-10-10-2 |
So I dumped the
Yes, there are Frameworks paths there, but the repo runfiles paths come first so they take precedence. It's just that there's no repo path for six, even though there are repo paths for all other dependencies. The same is true on my local linux machine, so I take it that both platforms are using the system-installed version of six, and in the case of Mac that version's just too old. I wonder why there's no repo for six. When I create a virtualenv and do |
Six doesn't appear as a dep in |
Ok, I've tracked it down. The python-dateutil package is the one that has the PyPI dependency on six. But if we inspect its generated Bazel target with Unpacking METADATA parsing problems are covered by issues #70 and #95. In the meantime we can also use the workaround in the first comment of #70 and manually declare the dependency in the test's requirements.txt file. |
Hi there,
I'm the Bazel release manager and I've been investigating the rules_python failures (https://buildkite.com/bazel/bazel-with-downstream-projects-bazel/builds/233#14f47bce-4863-42cf-9179-fe4b1be650a8) in the new release candidate for Bazel 0.14.0. After trying to reproduce this in my macOS I realized that the failures are also present with Bazel 0.12.0 as follows:
Given this I think the failures are unrelated to a recent change in Bazel itself.
The text was updated successfully, but these errors were encountered: