Debian Codegraph @

.aspect/bazelrc/convenience.bazelrc

raw
1 # Attempt to build & test every target whose prerequisites were successfully built.
2 # Docs: https://bazel.build/docs/user-manual#keep-going
3 build --keep_going
4
5 # Output test errors to stderr so users don't have to `cat` or open test failure log files when test
6 # fail. This makes the log noisier in exchange for reducing the time-to-feedback on test failures for
7 # users.
8 # Docs: https://bazel.build/docs/user-manual#test-output
9 test --test_output=errors
10
11 # Show the output files created by builds that requested more than one target. This helps users
12 # locate the build outputs in more cases
13 # Docs: https://bazel.build/docs/user-manual#show-result
14 build --show_result=20
15
16 # Bazel picks up host-OS-specific config lines from bazelrc files. For example, if the host OS is
17 # Linux and you run bazel build, Bazel picks up lines starting with build:linux. Supported OS
18 # identifiers are `linux`, `macos`, `windows`, `freebsd`, and `openbsd`. Enabling this flag is
19 # equivalent to using `--config=linux` on Linux, `--config=windows` on Windows, etc.
20 # Docs: https://bazel.build/reference/command-line-reference#flag--enable_platform_specific_config
21 common --enable_platform_specific_config
22
23 # Output a heap dump if an OOM is thrown during a Bazel invocation
24 # (including OOMs due to `--experimental_oom_more_eagerly_threshold`).
25 # The dump will be written to `<output_base>/<invocation_id>.heapdump.hprof`.
26 # You may need to configure CI to capture this artifact and upload for later use.
27 # Docs: https://bazel.build/reference/command-line-reference#flag--heap_dump_on_oom
28 common --heap_dump_on_oom