Skip to content

Bazel 6.X.X - runfiles output-directories does not respect workspace-name anymore #18128

@PieterBunnenberg

Description

@PieterBunnenberg

Description of the bug:

Starting with Bazel 6, the output directory for runfiles does not use the worskpace-name for the sub-directory anymore.

From the documentation:

foo/bar/baz.runfiles/ <== The runfiles symlink farm for the //foo/bar:baz executable.
MANIFEST
<workspace-name>/

With Bazel 5.X.X:
foo/bar/baz.runfiles/<workspace-name>

With Bazel 6.X.X:
foo/bar/baz.runfiles/_main

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

No response

Which operating system are you running Bazel on?

Linux

What is the output of bazel info release?

release 6.1.0

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

No response

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

No response

Have you found anything relevant by searching the web?

No response

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

No response

Metadata

Metadata

Assignees

Labels

P2We'll consider working on this in future. (Assignee optional)team-DocumentationDocumentation improvements that cannot be directly linked to other team labelsteam-ExternalDepsExternal dependency handling, remote repositiories, WORKSPACE file.type: bug

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions