github.com/lestrrat-go/jwx/v2@v2.0.21/.aspect/bazelrc/convenience.bazelrc (about)

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