From 7831d49a5136d82598a905bd0739ecaad98a99b6 Mon Sep 17 00:00:00 2001 From: Arkadiusz Jedrzejewski Date: Tue, 23 Jun 2026 09:30:39 +0200 Subject: [PATCH] bazel: use profile-update=atomic `bazel coverage` sometimes return negative count on U24. Use atomic profile update instead of ignoring the error. --- .bazelrc | 2 ++ .github/workflows/code_coverage.yml | 1 - 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/.bazelrc b/.bazelrc index aa622afbc..15d4aaa1a 100644 --- a/.bazelrc +++ b/.bazelrc @@ -30,6 +30,8 @@ coverage --features=coverage coverage --combined_report=lcov coverage --cache_test_results=no coverage --test_tag_filters=-no-coverage +coverage --copt=-fprofile-update=atomic +coverage --linkopt=-fprofile-update=atomic # Common Lifecycle Toolchain flags for build (do not use it in case of system toolchains!) build:toolchain_common --incompatible_strict_action_env diff --git a/.github/workflows/code_coverage.yml b/.github/workflows/code_coverage.yml index 3d75743ad..e729f195a 100644 --- a/.github/workflows/code_coverage.yml +++ b/.github/workflows/code_coverage.yml @@ -29,7 +29,6 @@ jobs: bazel-target: "//score/..." bazel-config: "x86_64-linux" extra-bazel-flags: "--test_output=errors --nocache_test_results --lockfile_mode=error" - genhtml-extra-flags: "--ignore-errors=negative" artifact-name-suffix: "_cpp" retention-days: 10 min-coverage: 76