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

Bazel bash completion script takes hours to build on macOS via MacPorts #4670

Closed
missa-prime opened this issue Feb 21, 2018 · 2 comments
Closed
Labels
area-EngProd Bazel CI, infrastructure, bootstrapping, release, and distribution tooling P3 We're not considering working on this, but happy to review a PR. (No assignee) team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website

Comments

@missa-prime
Copy link

missa-prime commented Feb 21, 2018

Description of the problem / feature request:

Essentially, it takes hours to build the Bazel bash completion script on macOS when attempting to install Bazel via MacPorts. Building Bazel itself from source takes only several minutes, but somehow the bash completion script takes hours. There seems to be a hang that ends up resolving itself if you wait long enough.

Feature requests: what underlying problem are you trying to solve with this feature?

N/A

Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

  1. Make sure JDK 8 or newer is installed
  2. Ensure that /etc/gitconfig file exists and user.name and user.email fields are populated
  3. Install MacPorts from here
  4. sudo port install bazel at a terminal prompt to install bazel

What operating system are you running Bazel on?

macOS 10.12.6

What's the output of bazel info release?

ERROR: The 'info' command is only supported from within a workspace.

Since I don't have a workspace handy, I'll provide the output of bazel version:

Build label: 0.9.0- (@non-git)
Build target: bazel-out/darwin-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Fri Aug 1 19:08:22 +50104 (1518980756902)
Build timestamp: 1518980756902
Build timestamp as int: 1518980756902

If bazel info release returns "development version" or "(@non-git)", tell us how you built Bazel.

Bazel was built from source while being installed with MacPorts.

What's the output of git remote get-url origin ; git rev-parse master ; git rev-parse HEAD ?

N/A

Have you found anything relevant by searching the web?

No.

Any other information, logs, or outputs that you want to share?

Here are traces captured by @kencu:

Sample.of.cfprefsd.txt
Sample.of.distnoted.txt
Sample.of.tclsh8.5.txt
Sample.of.lsd.txt
Sample.of.java4.txt
Sample.of.java3.txt
Sample.of.java2.txt
Sample.of.java1.txt

@missa-prime missa-prime changed the title Bazel bash completion script takes hours to build on macOs via MacPorts Bazel bash completion script takes hours to build on macOS via MacPorts Feb 21, 2018
@aehlig aehlig added type: feature request P3 We're not considering working on this, but happy to review a PR. (No assignee) category: misc > release / binary labels Feb 26, 2018
@missa-prime
Copy link
Author

Why is this tagged as a feature request rather than a bug?

@aiuto aiuto added area-EngProd Bazel CI, infrastructure, bootstrapping, release, and distribution tooling and removed category: misc > release / binary type: feature request labels Dec 10, 2018
@meisterT
Copy link
Member

I assume this issue is stale.

@philwo philwo added the team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website label Jun 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-EngProd Bazel CI, infrastructure, bootstrapping, release, and distribution tooling P3 We're not considering working on this, but happy to review a PR. (No assignee) team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website
Projects
None yet
Development

No branches or pull requests

5 participants