From 67cd361536138acf24cbbbc0290b4e87a7071b84 Mon Sep 17 00:00:00 2001 From: Daniel Wong Date: Tue, 18 Feb 2025 19:52:26 +0100 Subject: [PATCH] Tell tests (e.g. particularly canbench) to "show their true colors". What this literally does is sets the CLICOLOR_FORCE environment variable to true. This is a convention that different programs follow. In particular, the colored Rust library uses it (and canbench uses colored). --- bazel/conf/.bazelrc.build | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/bazel/conf/.bazelrc.build b/bazel/conf/.bazelrc.build index 3d741e450d1..f908653e2d0 100644 --- a/bazel/conf/.bazelrc.build +++ b/bazel/conf/.bazelrc.build @@ -141,3 +141,8 @@ common --remote_download_all # This option (in conjunction with remote cache issues) creates build failures # https://github.com/bazelbuild/bazel/issues/22387 common --noexperimental_inmemory_dotd_files + +# This is particularly helpful for canbench, but other tests that follow this +# convention would also benefit. If the test does not support this, this "almost +# certainly" does no harm. +test --test_env=CLICOLOR_FORCE=true