Skip to content

bazel coverage generating conflicting files with bazel 5.0rc3 #14521

@ptarjan

Description

@ptarjan

Description of the problem / feature request:

When trying to use bazel 5.0rc3 I'm seeing this error with our monorepo build:

(05:18:41) ERROR: file 'bazel/python/interpreter/container_py_runtime_pair/baseline_coverage.dat' is generated by these conflicting actions:
  | Label: //bazel/python/interpreter:container_py_runtime_pair
  | RuleClass: py_runtime_pair rule
  | Configuration: 600691a7f9d17ce0f14c6173af35efe5e71db5a8ec4a2a4fcd279b10553a5c30
  | Mnemonic: BaselineCoverage
  | Action key: ee6504712039128a28b0e61d43c28805c6556a4fc52e6a180ea70faa846acc1b, c4ad6d14fd016359eed85dd1130a3a6c09f6bbdddddd4bf639897ecfd16f7c2d
  | Progress message: Writing file bazel/python/interpreter/container_py_runtime_pair/baseline_coverage.dat
  | PrimaryInput: (null)
  | PrimaryOutput: File:[[<execution_root>]bazel-out/k8-fastbuild/testlogs]bazel/python/interpreter/container_py_runtime_pair/baseline_coverage.dat
  | Owner information: ToolchainDependencyConfiguredTargetKey{label=//bazel/python/interpreter:container_py_runtime_pair, config=BuildConfigurationValue.Key[600691a7f9d17ce0f14c6173af35efe5e71db5a8ec4a2a4fcd279b10553a5c30], executionPlatformLabel=@io_bazel_rules_docker//platforms:local_container_platform}, ConfiguredTargetKey{label=//bazel/python/interpreter:container_py_runtime_pair, config=BuildConfigurationValue.Key[600691a7f9d17ce0f14c6173af35efe5e71db5a8ec4a2a4fcd279b10553a5c30]}
  | MandatoryInputs: are equal
  | Outputs: are equal
  | (05:18:41) WARNING: errors encountered while analyzing target '//bazel/python/interpreter:container_py_runtime_pair': it will not be built
  | (05:18:41) ERROR: file 'external/local_config_cc/cc-compiler-k8/baseline_coverage.dat' is generated by these conflicting actions:
  | Label: @local_config_cc//:cc-compiler-k8
  | RuleClass: cc_toolchain rule
  | Configuration: 600691a7f9d17ce0f14c6173af35efe5e71db5a8ec4a2a4fcd279b10553a5c30
  | Mnemonic: BaselineCoverage
  | Action key: ee6504712039128a28b0e61d43c28805c6556a4fc52e6a180ea70faa846acc1b, c4ad6d14fd016359eed85dd1130a3a6c09f6bbdddddd4bf639897ecfd16f7c2d
  | Progress message: Writing file external/local_config_cc/cc-compiler-k8/baseline_coverage.dat
  | PrimaryInput: (null)
  | PrimaryOutput: File:[[<execution_root>]bazel-out/k8-fastbuild/testlogs]external/local_config_cc/cc-compiler-k8/baseline_coverage.dat
  | Owner information: ToolchainDependencyConfiguredTargetKey{label=@local_config_cc//:cc-compiler-k8, config=BuildConfigurationValue.Key[600691a7f9d17ce0f14c6173af35efe5e71db5a8ec4a2a4fcd279b10553a5c30], executionPlatformLabel=@io_bazel_rules_docker//platforms:local_container_platform}, ToolchainDependencyConfiguredTargetKey{label=@local_config_cc//:cc-compiler-k8, config=BuildConfigurationValue.Key[600691a7f9d17ce0f14c6173af35efe5e71db5a8ec4a2a4fcd279b10553a5c30], executionPlatformLabel=@local_config_platform//:host}
  | MandatoryInputs: are equal
  | Outputs: are equal

Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Sadly I haven't isolated which rules are actually causing this. Maybe you can help me get you the right debugging information?

What operating system are you running Bazel on?

Linux

What's the output of bazel info release?

$ bazel info release
INFO: Invocation ID: e7ad3ee9-85ab-4ac0-8179-69dab199ad4a
release 5.0.0rc3

If bazel info release returns "development version" or "(@Non-Git)", tell us how you built Bazel.

Replace this line with your answer.

What's the output of git remote get-url origin ; git rev-parse master ; git rev-parse HEAD ?

Private repo

Have you found anything relevant by searching the web?

No

Any other information, logs, or outputs that you want to share?

Replace this line with your answer.

Metadata

Metadata

Assignees

Labels

P2We'll consider working on this in future. (Assignee optional)coverageteam-Rules-ServerIssues for serverside rules included with Bazeltype: bug

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions