Skip to content

Commit

Permalink
Stop including progress messages in the execution log.
Browse files Browse the repository at this point in the history
They're fairly verbose and represent a significant portion of the log, much more so once we switch to a compact format. It should be possible to uniquely identify spawns through a combination of mnemonic, target label and output path.

Progress on bazelbuild/bazel#18643.

PiperOrigin-RevId: 582273738
  • Loading branch information
tjgq authored and copybara-github committed Nov 14, 2023
1 parent 21eb7ab commit b7e97fd
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions third_party/bazel/src/main/protobuf/spawn.proto
Original file line number Diff line number Diff line change
Expand Up @@ -139,9 +139,6 @@ message SpawnExec {
// The Spawn timeout.
int64 timeout_millis = 8;

// A user-friendly text message representing the spawn progress.
string progress_message = 9;

// An opaque string that identifies the type of the Spawn's action.
string mnemonic = 10;

Expand Down Expand Up @@ -191,4 +188,6 @@ message SpawnExec {

// Timing, size and memory statistics.
SpawnMetrics metrics = 20;

reserved 9;
}

0 comments on commit b7e97fd

Please sign in to comment.