diff options
| author |  Benjamin Peterson <bp@benjamin.pe> | 2018-05-03 04:30:19 -0700 |
|---|---|---|
| committer |  Copybara-Service <copybara-piper@google.com> | 2018-05-03 04:32:12 -0700 |
| commit | 7e1c7bcd4215a20479963ec34c8d7b685f393cc6 (patch) | |
| tree | 7dd4d13f52c52cc3a41b03ebc2035840eb32969d /src/main/java/com/google/devtools/build/lib/exec | |
| parent | 8ac2fb1ff86a8a08d1a53888ae5adf901becd2b9 (diff) | |
Report what RemoteSpawnCache is doing.
Post ProgressStatus.CHECKING_CACHE if RemoteSpawnCache is checking the cache.
The UI sees CHECKING_CACHE exactly the same as EXECUTING because no UIs
currently have any special behavior for actions in cache-lookup state. This is
still a UX improvement with --experimental_spawn_cache because EXECUTING is
generally more correct than the old action state, which varies from harmless but
unhelpful (no known state) to just wrong (C++ compile actions claimed they were
doing include scanning during cache lookups).
Closes #5130.
Change-Id: I77421c3667c180875216f937fe0713f0e9415a7a
PiperOrigin-RevId: 195233123
Diffstat (limited to 'src/main/java/com/google/devtools/build/lib/exec')
| -rw-r--r-- | src/main/java/com/google/devtools/build/lib/exec/AbstractSpawnStrategy.java | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/src/main/java/com/google/devtools/build/lib/exec/AbstractSpawnStrategy.java b/src/main/java/com/google/devtools/build/lib/exec/AbstractSpawnStrategy.java index d9ae236622..d8c42ff140 100644 --- a/src/main/java/com/google/devtools/build/lib/exec/AbstractSpawnStrategy.java +++ b/src/main/java/com/google/devtools/build/lib/exec/AbstractSpawnStrategy.java @@ -252,6 +252,7 @@ public abstract class AbstractSpawnStrategy implements SandboxedSpawnActionConte EventBus eventBus = actionExecutionContext.getEventBus(); switch (state) { case EXECUTING: + case CHECKING_CACHE: eventBus.post(ActionStatusMessage.runningStrategy(action, name)); break; case SCHEDULING: |