local/install_deps.bash seems to fail mysteriously when there isn't enough memory

[evverx]

I launched a VM where install_deps.bash failed with

Running: bazel run //local:create_gopath 2>/dev/null
| Return code is non-zero (1).
| Exit.

, which wasn't very helpful. Without 2 >/dev/null I was able to figure out what happened but unfortunately additionally broke something else because apparently the output is used to set GOPATH :-) I think it would be great if the output wasn't sent to "/dev/null" here.

(I relaxed the limits a bit and got past install_deps.bash and now python butler.py run_server --bootstrap seems to be stuck trying to "build templates for App Engine". The machine is totally unresponsive so it's hard to tell what's going on. I'm going to tweak the limits until it works but it would probably be useful to mention in the documentation how a "typical" machine is supposed to look like, that is something like https://github.com/google/oss-fuzz/blob/master/docs/faq.md#what-are-the-specs-on-your-machines maybe).

[evverx]

The machine is totally unresponsive

Judging by "Out of memory: Kill process 2299 (node) score 115 or sacrifice child", it was the OOM killer that was busy destroying "polymer-bundler". I hope 32Gb will suffice.

[Dor1s]

That's really weird, I don't think you need any beefy machine for that. Which OS are you trying this on?

[evverx]

That was Ubuntu 18.04.1 LTS run on top of macOS Mojave with VirtualBox.

[evverx]

Anyway, I kind of found an abandoned beefy machine :-) and everything seems to be working as far as I can tell. I don't think I'll start to dig deeper anytime soon so I think the issue can safely be closed.

And, by the way, congratulations on open-sourcing ClusterFuzz!

[inferno-chromium]

Reopening to improve the things mentioned in c#0.

[inferno-chromium]

bazel does not support a quite mode, so everything gets dumped to stderr - https://groups.google.com/forum/#!topic/bazel-discuss/JVCotYRXeyk

till then i will fix this to make it more obvious where we are running this command, like this is run in 'src' subdir. maybe also update code with comment.

[inferno-chromium]

polymer_bundler will be tracked by its own issue. bazel issue should be fixed now. Thanks for the report.