hermetic_cc_toolchain/.bazelrc

test --sandbox_default_allow_network=false
test --test_output=errors

build --verbose_failures
build --worker_sandboxing

build --experimental_reuse_sandbox_directories
build --incompatible_enable_cc_toolchain_resolution
build --action_env BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1

try-import %workspace%/.custom.ci.bazelrc
bring back some things from the old repo 2021-06-07 22:50:19 +03:00			`test --sandbox_default_allow_network=false`
Initial commit with minimal examples 2021-04-10 01:05:01 +03:00			`test --test_output=errors`
[bazelrc] build --compilation_mode=opt 2021-12-15 15:05:07 +02:00
			`build --verbose_failures`
Initial commit with minimal examples 2021-04-10 01:05:01 +03:00			`build --worker_sandboxing`
remove non-required options from .bazelrc 2021-06-30 16:00:42 +03:00
tests: sandboxing The slowness of bazel-zig-cc comes from setup and teardown of sandbox directories[1]. Turning on `experimental_reuse_sandbox_directories` speeds it up significantly. Depending on how the tests with this go in the next few days, I will add this recommendation to README. This has been marked as safe to use and no longer experimental as of Bazel master[2]. [1]: https://git.sr.ht/~motiejus/test-zigcc [2]: https://github.com/bazelbuild/bazel/pull/16490 2022-12-12 10:24:52 +02:00			`build --experimental_reuse_sandbox_directories`
Initial commit with minimal examples 2021-04-10 01:05:01 +03:00			`build --incompatible_enable_cc_toolchain_resolution`
Add libc constraint and libc aware toolchains - Also get rid of @bazel_skylib dependency 2022-04-13 17:52:25 +03:00			`build --action_env BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1`
More CI (#3) - ci only: use a separate zig cache dir for each run - use `tools/bazel` everywhere. - remove arm64 tests. They don't give enough value to be worth the brittle environment. - remove windows execution, except for launcher. Ditto. I will probably bring them back. 2023-03-06 17:32:48 +02:00
			`try-import %workspace%/.custom.ci.bazelrc`