tree e912d3e33eeaa7a00de81cf53439b2493732cfd8
parent ea0f062d4ed2fd5b90e1870b6c23d796113a9786
author adonovan <adonovan@google.com> 1584564407 -0700
committer Copybara-Service <copybara-worker@google.com> 1584564488 -0700

bazel: add --max_computation_steps flag

This change adds a --max_computation_steps=<n> flag that imposes a limit on the
number of abstract computation steps to execute a single BUILD file.
Its default value is zero, meaning no limit.
The count is deterministic, and is retained in the package metadata.

Abstract computation steps are currently eval, exec, and assign operations in
the tree-walking interpreter, but in future they will mean byte code instructions;
the two measures are incommensurable.

There is no corresponding flag for .bzl files, but they typically
do little more than execute def statements.

In the Usual Benchmark, the minimum limit for success is 4.2e6 steps,
but individual whoppers are readily found in Google's code base that
exceed 5e8 steps.

RELNOTES: The --max_computation_steps flag bounds the computation done by a BUILD file.
PiperOrigin-RevId: 301658760