Skip to content

incompatible_use_new_cgroup_implementation #28244

@zhengwei143

Description

@zhengwei143

Motivation

This is a new implementation of cgroups (#21322) that extends functionality of cgroups (used by worker / sandboxed spawns) to also enable CPU limiting as well.

Description

The flip of this flag will cause the following flags (if specified) to take effect (when previously they were a NO-OP):

  • --experimental_sandbox_limits
  • --experimental_sandbox_enforce_resources_regexp

These flags affect how limits get applied on certain actions.

Incompatible Flag

incompatible_use_new_cgroup_implementation

Migration Guide

The implications are likely going to be minimal, as these flags are less likely to have already been used if --incompatible_use_new_cgroup_implementation has not already been flipped by the user. As such, for most users, this should be a NO-OP.

If this does end up affecting your build, then the user can update --experimental_sandbox_limits and --experimental_sandbox_enforce_resources_regexp accordingly.

In which Bazel LTS version will this incompatible change be enabled?

Bazel 9

Additional Context

No response

TODO List

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2We'll consider working on this in future. (Assignee optional)incompatible-changeIncompatible/breaking changeteam-Local-ExecIssues and PRs for the Execution (Local) teamteam-PerformanceIssues for Performance teams

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions