What steps will reproduce the problem?
1. Specify memory limits that are too high for the JVM
2. Run w/o verbose and get the following message:
Caused by: java.io.IOException: Could not open the pipe from the worker. Either the worker has likely crashed or the VM could not start up within the specified time limit (1m). Run with --verbose to see any worker output.
4. Run w/ verbose and get the following message:
[trial-0] Invalid maximum heap size: -Xmx10g
[trial-0] The specified size exceeds the maximum representable size.
Should probably propagate that error message up, regardless of whether or not
verbose is on.
Original issue reported on code.google.com by kak@google.com on 10 Nov 2012 at 6:16
Original issue reported on code.google.com by
kak@google.com
on 10 Nov 2012 at 6:16