From 39b18cae5102e7a10272ef2752461c2287d4493d Mon Sep 17 00:00:00 2001 From: Ulf Adams Date: Mon, 2 Nov 2015 08:45:26 +0000 Subject: Remove BlazeRuntime.reporter; use a BlazeModule to attach event handlers. This only affects tests that previously set a Reporter on the BlazeRuntime; the production code is already using the per-command Reporter in all cases. -- MOS_MIGRATED_REVID=106820846 --- .../com/google/devtools/build/lib/runtime/BlazeCommandDispatcher.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/main/java/com/google/devtools/build/lib/runtime/BlazeCommandDispatcher.java') diff --git a/src/main/java/com/google/devtools/build/lib/runtime/BlazeCommandDispatcher.java b/src/main/java/com/google/devtools/build/lib/runtime/BlazeCommandDispatcher.java index 100a075d92..2235eb80cf 100644 --- a/src/main/java/com/google/devtools/build/lib/runtime/BlazeCommandDispatcher.java +++ b/src/main/java/com/google/devtools/build/lib/runtime/BlazeCommandDispatcher.java @@ -206,7 +206,7 @@ public class BlazeCommandDispatcher { * client process, or throws {@link ShutdownBlazeServerException} to * indicate that a command wants to shutdown the Blaze server. */ - public int exec(List args, OutErr outErr, long firstContactTime) + int exec(List args, OutErr outErr, long firstContactTime) throws ShutdownBlazeServerException { // Record the start time for the profiler and the timestamp granularity monitor. Do not put // anything before this! -- cgit v1.2.3