@@ -76,14 +76,16 @@ build:x86_64-linux --extra_toolchains=@score_toolchains_rust//toolchains/ferroce
7676# With this instrumentation filter for our two main components, we ensure that `bazel coverage //...` is yielding the correct results
7777coverage --config=x86_64-linux
7878coverage --instrumentation_filter="^//score/datarouter[/:],^//score/mw/log[/:],-//score/mw/.*/test[/:]"
79- coverage --experimental_generate_llvm_lcov
80- coverage --experimental_use_llvm_covmap
79+ # Note: LLVM-specific flags - only use with LLVM/Clang toolchain
80+ # coverage --experimental_generate_llvm_lcov
81+ # coverage --experimental_use_llvm_covmap
82+ # coverage --test_env=LLVM_PROFILE_CONTINUOUS_MODE=1
83+ # coverage --cxxopt -mllvm
84+ # coverage --cxxopt -runtime-counter-relocation
85+
86+ # GCC-based coverage configuration
8187coverage --combined_report=lcov
8288coverage --coverage_report_generator=@bazel_tools//tools/test/CoverageOutputGenerator/java/com/google/devtools/coverageoutputgenerator:Main
8389coverage --test_env=COVERAGE_GCOV_OPTIONS=-bcu
84- # TODO set toolchain feature once possible
85- # These compile time options are required to cover abnormal termination cases. In GCC one can use `__gcc_dump()`, but this does not work with LLVM
86- # LLVM provided these compile-time options in combination with a specific profile setting which is enabled in bazel via `LLVM_PROFILE_CONTINUOUS_MODE`
87- coverage --test_env=LLVM_PROFILE_CONTINUOUS_MODE=1
88- coverage --cxxopt -mllvm
89- coverage --cxxopt -runtime-counter-relocation
90+ coverage --features=coverage
91+ coverage --cache_test_results=no
0 commit comments