From 5960674c8fe086413c3ef88b29fbb4c6f4c4ca3f Mon Sep 17 00:00:00 2001 From: Rahat Mahmood Date: Tue, 4 May 2021 17:38:00 -0700 Subject: Document how to handle build failures from go-marshal verbosity. With debugging enabled, go-marshal can generate too much output for bazel under default configurations, which can cause builds to fail. The limit defaults to 1 MB. PiperOrigin-RevId: 372030402 --- tools/go_marshal/README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tools/go_marshal/README.md b/tools/go_marshal/README.md index eddba0c21..bbd4c9f48 100644 --- a/tools/go_marshal/README.md +++ b/tools/go_marshal/README.md @@ -140,3 +140,6 @@ options, depending on how go-marshal is being invoked: - Set `debug = True` on the `go_marshal` BUILD rule. - Pass `-debug` to the go-marshal tool invocation. + +If bazel complains about stdout output being too large, set a larger value +through `--experimental_ui_max_stdouterr_bytes`, or `-1` for unlimited output. -- cgit v1.2.3