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 run probably fails on long classpaths #1392

Closed
ekuefler opened this issue Jun 13, 2016 · 2 comments
Closed

bazel run probably fails on long classpaths #1392

ekuefler opened this issue Jun 13, 2016 · 2 comments
Labels
category: misc > misc P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) type: bug

Comments

@ekuefler
Copy link
Contributor

This report is based off reading source code rather than something I've actually repro'd, so apologies if I'm missing something.

Linux tends to limit the max length of a command line to around 128k. This can be a problem for Bazel java compilation since it requires jars for every transitive dep to be specified in the classpath. The java run script attempts to mitigate this by echoing the classpath to a file and using it as an @argfile. But argfiles are only implemented in stock JDK in Java 9, which public Bazel isn't using. So I believe this will fail if anyone tries to bazel run a Java binary with a large number of transitive deps.

@hermione521
Copy link
Contributor

Guess it's a bug. But will label as P4 because I failed to repro. (Got Java "too many constants" JVM error before this "bug")

@hermione521 hermione521 added type: bug P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) category: misc > misc and removed under investigation labels Jun 17, 2016
@aiuto
Copy link
Contributor

aiuto commented Mar 28, 2019

Closing as "Won't Fix - obsolete".
It was not reproducible and we have moved beyond the JVMs in question.

@aiuto aiuto closed this as completed Mar 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: misc > misc P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) type: bug
Projects
None yet
Development

No branches or pull requests

3 participants