netbird/gvisor
0
0
Fork 0
mirror of https://github.com/netbirdio/gvisor.git synced 2026-05-22 17:12:49 -07:00
Code Issues Packages Projects Releases Wiki Activity

Document how to handle build failures from go-marshal verbosity.

Browse Source 
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
This commit is contained in:
Rahat Mahmood
2021-05-04 17:40:08 -07:00
committed by gVisor bot
parent 689b369f57
commit 5960674c8f
1 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tools/go_marshal/README.md
+3
View File
@@ -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.