[StackOverflow/go] Bazel coverage with cache

### ROOT CAUSE The issue arises due to a misconfiguration in the Bazel coverage setup, where the cache is not properly integrated with the coverage tooling. Specifically, the `--coverage` flag and the `--cache` flag may conflict, leading to incomplete or inaccurate coverage reports. This could be caused by: 1. Incorrect order of flags or arguments in the Bazel command. 2. The cache not being invalidated when code changes, resulting in stale coverage data. 3. The coverage tool not being aware of the cache's state, leading to overlapping or missing coverage data. ### CODE FIX 1. **Update Bazel Configuration**: Ensure that the `bazelrc` or build flags correctly prioritize the `--coverage` and `--cache` flags. For example: ```bash build --coverage --cache_path=/path/to/cache ``` 2. **Invalidate Cache on Coverage Runs**: Add a script to clear the cache before running coverage to ensure fresh data: ```bash ./clean_cache.sh && bazel test --coverage --cache_path=/path/to/cache //... ``` 3. **Use Bazel's Coverage Integration**: Leverage Bazel's built-in coverage support by ensuring the `--test_output=coverage` flag is used alongside `--cache`: ```bash bazel test --test_output=coverage --cache_path=/path/to/cache //... ``` 4. **Check for Conflicting Rules**: Review any custom Bazel rules or `.bazelrc` configurations that might interfere with coverage caching. Remove any redundant or conflicting flags. For detailed steps, refer to the [Bazel Coverage Documentation](https://bazel.build/docs/build#coverage).