diff options
| author | Rahat Mahmood <rahat@google.com> | 2021-05-04 17:38:00 -0700 |
|---|---|---|
| committer | gVisor bot <gvisor-bot@google.com> | 2021-05-04 17:40:08 -0700 |
| commit | 5960674c8fe086413c3ef88b29fbb4c6f4c4ca3f (patch) | |
| tree | 650ccf51b8b7aa021980c87beaea9a6c8d085b6a /tools/go_marshal | |
| parent | 689b369f5788c15f9b018246baa4e318082c0d79 (diff) | |
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
Diffstat (limited to 'tools/go_marshal')
| -rw-r--r-- | tools/go_marshal/README.md | 3 |
1 files changed, 3 insertions, 0 deletions
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. |