package tools.protos

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message Digest

spawn.proto:31

Digest of a file or action cache entry.

Used in: ExecLogEntry.File, ExecLogEntry.Spawn, File, SpawnExec

message EnvironmentVariable

spawn.proto:60

Contents of command environment.

Used in: ExecLogEntry.Spawn, SpawnExec

message ExecLogEntry

spawn.proto:219

An entry in the compact log format. This is the format generated by --experimental_execution_log_compact_file. Each entry describes either an executed spawn or non-spawn action or a piece of data referenced by other entries. This considerably reduces the runtime overhead and the size of the log when compared to the --execution_log_{binary,json}_file formats. To ensure that the log can be parsed in a single pass, every entry must be serialized after all other entries it references by ID. However, entries aren't guaranteed to be serialized in increasing ID order. Entries other than spawns and non-spawn actions may not be assumed to be canonical. For performance reasons, the same file, directory or input set may be serialized multiple times with a different ID.

message ExecLogEntry.Directory

spawn.proto:249

An input or output directory. May be a source directory, a fileset tree, or a tree artifact.

Used in: ExecLogEntry

message ExecLogEntry.File

spawn.proto:238

An input or output file.

Used in: ExecLogEntry, Directory, RunfilesTree

message ExecLogEntry.InputSet

spawn.proto:271

A set of spawn inputs. The contents of the set are the directly contained entries in addition to the contents of all transitively referenced sets. When order matters, transitive sets come before direct entries and within a set, entries are considered in left-to-right order ("postorder"). Sets are not canonical: two sets with different structure may yield the same contents.

Used in: ExecLogEntry

message ExecLogEntry.Invocation

spawn.proto:222

Information pertaining to the entire invocation. May appear at most once in the initial position.

Used in: ExecLogEntry

message ExecLogEntry.Output

spawn.proto:348

A spawn output.

Used in: Spawn

message ExecLogEntry.RunfilesTree

spawn.proto:314

A structured representation of the .runfiles directory of an executable. Instead of storing the directory directly, the tree is represented similarly to its in-memory representation in Bazel and needs to be reassembled from the following parts (in case of path collisions, later entries overwrite earlier ones): 1. symlinks (symlinks_id) 2. artifacts at canonical locations (input_set_id) 3. empty files (empty_files) 4. root symlinks (root_symlinks_id) 5. the _repo_mapping file with the repo mapping manifest (repo_mapping_manifest) 6. the <workspace runfiles directory>/.runfile file (if the workspace runfiles directory wouldn't exist otherwise) See SpawnLogReconstructor#reconstructRunfilesDir for details.

Used in: ExecLogEntry

message ExecLogEntry.Spawn

spawn.proto:363

An executed spawn.

Used in: ExecLogEntry

message ExecLogEntry.SymlinkAction

spawn.proto:422

A symlink action, which is not backed by a spawn.

Used in: ExecLogEntry

message ExecLogEntry.SymlinkEntrySet

spawn.proto:288

A collection of runfiles symlinked at custom locations. The contents of the set are the directly contained entries in addition to the contents of all transitively referenced sets. When order matters, transitive sets come before direct entries and within a set, entries are considered in left-to-right order ("postorder"). Sets are not canonical: two sets with different structure may yield the same contents.

Used in: ExecLogEntry

An unresolved symlink.

Used in: ExecLogEntry

message File

spawn.proto:42

Used in: SpawnExec

message Platform

spawn.proto:67

Command execution platform. This message needs to be kept in sync with [Platform][google.devtools.remoteexecution.v1test.Platform].

Used in: ExecLogEntry.Spawn, SpawnExec

message Platform.Property

spawn.proto:68

Used in: Platform

message SpawnExec

spawn.proto:127

Each message contains an executed command, its full inputs and outputs, and other information. This format is relatively costly to produce and results in very large files, due to the amount of repeated information. The --experimental_execution_log_compact_file format provides a better alternative.

message SpawnMetrics

spawn.proto:76

Timing, size, and memory statistics for a SpawnExec.

Used in: ExecLogEntry.Spawn, SpawnExec