Add basic perf tests for chromoting protocol.

Add basic perf tests for chromoting protocol.

This CL doesn't yet include any emulation of network
characteristics (latency, bandwidth, etc.). I'm going to
implement it in a separate CL.

BUG=394067
TBR=ttuttle@chromium.org (DEPS on net in remoting/test)
http://crrev.com/285429

[Wez, 2014-07-16 22:44:52]

https://codereview.chromium.org/394883008/diff/10018/remoting/remoting_test.gypi
File remoting/remoting_test.gypi (right):

https://codereview.chromium.org/394883008/diff/10018/remoting/remoting_test.g...
remoting/remoting_test.gypi:385: 'test/protocol_perf_test.cc',
nit: name this _perftest.cc for consistency?

[rmsousa, 2014-07-16 23:06:00]

https://codereview.chromium.org/394883008/diff/1/remoting/client/chromoting_c...
File remoting/client/chromoting_client.h (right):

https://codereview.chromium.org/394883008/diff/1/remoting/client/chromoting_c...
remoting/client/chromoting_client.h:52: void set_candidate_config(
is this a testing hook? if so, please add a comment.

https://codereview.chromium.org/394883008/diff/1/remoting/host/fake_screen_ca...
File remoting/host/fake_screen_capturer.cc (right):

https://codereview.chromium.org/394883008/diff/1/remoting/host/fake_screen_ca...
remoting/host/fake_screen_capturer.cc:103:
frame->mutable_updated_region()->SetRect(
I'm not sure how this updated region detection works - does this affect how VP8
encodes the frame?

https://codereview.chromium.org/394883008/diff/1/remoting/protocol/connection...
File remoting/protocol/connection_to_host.h (right):

https://codereview.chromium.org/394883008/diff/1/remoting/protocol/connection...
remoting/protocol/connection_to_host.h:89: void
set_candidate_config(scoped_ptr<CandidateSessionConfig> config);
nit, feel free to ignore:
this name (and the corresponding class name) is a bit confusing.

Before I saw the actual code, I assumed candidate_config to be something
configuring candidates (like transport candidates), not a configuration
candidate (i.e. tentative configuration).

Since there is already a precedent for set_protocol_config (on the host side), I
suggest following that pattern instead, but I'm fine if you prefer to keep the
current name to match the underlying class.

https://codereview.chromium.org/394883008/diff/1/remoting/remoting_host.gypi
File remoting/remoting_host.gypi (right):

https://codereview.chromium.org/394883008/diff/1/remoting/remoting_host.gypi#...
remoting/remoting_host.gypi:429: 'host/setup/me2me_native_messaging_host.h',
Is this a leftover from another CL? unrelated clean-up?

https://codereview.chromium.org/394883008/diff/1/remoting/test/protocol_perf_...
File remoting/test/protocol_perf_test.cc (right):

https://codereview.chromium.org/394883008/diff/1/remoting/test/protocol_perf_...
remoting/test/protocol_perf_test.cc:306: LOG(ERROR) << "Frame rate: " << (40.0 /
elapsed.InSecondsF());
Nit: LOG(INFO)?

https://codereview.chromium.org/394883008/diff/1/remoting/test/protocol_perf_...
remoting/test/protocol_perf_test.cc:324:
current_frame_.reset(webrtc::SharedDesktopFrame::Wrap(
If you don't write anything to the frame, will it be blank or have garbage
pixels?
I suppose it doesn't matter for VERBATIM, but that makes this unusable with VP8
(either too cheap or too expensive to encode, depending on blank vs random). You
should either call out that this should only be used with Verbatim, or wrap this
around FakeScreenCapturer::DefaultFrameGenerator.

[Wez, 2014-07-16 23:16:40]

https://codereview.chromium.org/394883008/diff/1/remoting/client/chromoting_c...
File remoting/client/chromoting_client.h (right):

https://codereview.chromium.org/394883008/diff/1/remoting/client/chromoting_c...
remoting/client/chromoting_client.h:52: void set_candidate_config(
On 2014/07/16 23:06:00, rmsousa wrote:
> is this a testing hook? if so, please add a comment.

Better still, call it SetCandidateConfigForTest(), so that production code can't
call it. ^.^

[Sergey Ulanov, 2014-07-17 01:47:59]

https://codereview.chromium.org/394883008/diff/1/remoting/client/chromoting_c...
File remoting/client/chromoting_client.h (right):

https://codereview.chromium.org/394883008/diff/1/remoting/client/chromoting_c...
remoting/client/chromoting_client.h:52: void set_candidate_config(
On 2014/07/16 23:16:39, Wez wrote:
> On 2014/07/16 23:06:00, rmsousa wrote:
> > is this a testing hook? if so, please add a comment.
> 
> Better still, call it SetCandidateConfigForTest(), so that production code
can't
> call it. ^.^

Done.

https://codereview.chromium.org/394883008/diff/1/remoting/host/fake_screen_ca...
File remoting/host/fake_screen_capturer.cc (right):

https://codereview.chromium.org/394883008/diff/1/remoting/host/fake_screen_ca...
remoting/host/fake_screen_capturer.cc:103:
frame->mutable_updated_region()->SetRect(
On 2014/07/16 23:06:00, rmsousa wrote:
> I'm not sure how this updated region detection works - does this affect how
VP8
> encodes the frame?

Yes, it hints the VP8 which parts of the frame have changed and VP8 doesn't try
to encode anything outside of that region. Updated this code to generate
update_region() correctly.

https://codereview.chromium.org/394883008/diff/1/remoting/protocol/connection...
File remoting/protocol/connection_to_host.h (right):

https://codereview.chromium.org/394883008/diff/1/remoting/protocol/connection...
remoting/protocol/connection_to_host.h:89: void
set_candidate_config(scoped_ptr<CandidateSessionConfig> config);
On 2014/07/16 23:06:00, rmsousa wrote:
> nit, feel free to ignore:
> this name (and the corresponding class name) is a bit confusing.
> 
> Before I saw the actual code, I assumed candidate_config to be something
> configuring candidates (like transport candidates), not a configuration
> candidate (i.e. tentative configuration).
> 
> Since there is already a precedent for set_protocol_config (on the host side),
I
> suggest following that pattern instead, but I'm fine if you prefer to keep the
> current name to match the underlying class.

Yeah I agree, that it might be confusing, but set_protocol_config() might be
equally confusing. There is a config() in this class that returns negotiated
protocol config. candidate_config is a term that's already used in other places,
e.g. in JingleSession there candidate_config() and config().

I renamed the new method in ChromotingClient to SetProtocolConfigForTests() - to
match what we have in the ChromotingHost.

https://codereview.chromium.org/394883008/diff/1/remoting/remoting_host.gypi
File remoting/remoting_host.gypi (right):

https://codereview.chromium.org/394883008/diff/1/remoting/remoting_host.gypi#...
remoting/remoting_host.gypi:429: 'host/setup/me2me_native_messaging_host.h',
On 2014/07/16 23:06:00, rmsousa wrote:
> Is this a leftover from another CL? unrelated clean-up?

Yes.

https://codereview.chromium.org/394883008/diff/1/remoting/test/protocol_perf_...
File remoting/test/protocol_perf_test.cc (right):

https://codereview.chromium.org/394883008/diff/1/remoting/test/protocol_perf_...
remoting/test/protocol_perf_test.cc:306: LOG(ERROR) << "Frame rate: " << (40.0 /
elapsed.InSecondsF());
On 2014/07/16 23:06:00, rmsousa wrote:
> Nit: LOG(INFO)?

Done.

https://codereview.chromium.org/394883008/diff/1/remoting/test/protocol_perf_...
remoting/test/protocol_perf_test.cc:324:
current_frame_.reset(webrtc::SharedDesktopFrame::Wrap(
On 2014/07/16 23:06:00, rmsousa wrote:
> If you don't write anything to the frame, will it be blank or have garbage
> pixels?
It will contain garbage. BasicDesktopFrame() just mallocs the buffer, but
doesn't write anything into it.

> I suppose it doesn't matter for VERBATIM, but that makes this unusable with
VP8
> (either too cheap or too expensive to encode, depending on blank vs random).
You
> should either call out that this should only be used with Verbatim, or wrap
this
> around FakeScreenCapturer::DefaultFrameGenerator.

Added a comment that this class is intended to be used only with VERBATIM codec.

https://codereview.chromium.org/394883008/diff/10018/remoting/remoting_test.gypi
File remoting/remoting_test.gypi (right):

https://codereview.chromium.org/394883008/diff/10018/remoting/remoting_test.g...
remoting/remoting_test.gypi:385: 'test/protocol_perf_test.cc',
On 2014/07/16 22:44:52, Wez wrote:
> nit: name this _perftest.cc for consistency?

Done.

[Sergey Ulanov, 2014-07-21 17:45:19]

ping

[rmsousa, 2014-07-21 19:53:48]

lgtm

[Sergey Ulanov, 2014-07-21 19:56:59]

The CQ bit was checked by sergeyu@chromium.org

[commit-bot: I haz the power, 2014-07-21 19:59:14]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/sergeyu@chromium.org/394883008/70001

[commit-bot: I haz the power, 2014-07-21 20:17:10]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  android_aosp on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_aosp/builds/9...)
  android_chromium_gn_compile_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_chromium_gn_c...)
  android_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_clang_dbg/bui...)
  android_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_dbg/builds/20...)
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)
  ios_dbg_simulator on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_dbg_simulator/bui...)
  ios_rel_device on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device/builds...)
  ios_rel_device_ninja on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device_ninja/...)
  linux_chromium_chromeos_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)
  linux_chromium_chromeos_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)
  linux_chromium_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_clang_...)
  linux_chromium_gn_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_gn_rel...)
  linux_chromium_rel_swarming on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_rel_sw...)
  mac_chromium_compile_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/mac_chromium_compile_...)
  mac_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/mac_chromium_rel/buil...)
  win8_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win8_chromium_rel/bui...)
  win_chromium_compile_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_compile_...)
  win_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_rel/buil...)
  win_chromium_x64_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_x64_rel/...)
  linux_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/linux_gpu/builds/...)
  mac_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/mac_gpu/builds/31170)
  win_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/win_gpu/builds/35572)

[commit-bot: I haz the power, 2014-07-21 20:18:48]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-07-21 20:18:49]

Try jobs failed on following builders:
  mac_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/mac_gpu/builds/31178)

[Sergey Ulanov, 2014-07-22 20:37:56]

The CQ bit was checked by sergeyu@chromium.org

[commit-bot: I haz the power, 2014-07-22 20:38:30]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/sergeyu@chromium.org/394883008/90001

[Sergey Ulanov, 2014-07-22 20:43:57]

The CQ bit was unchecked by sergeyu@chromium.org

[Sergey Ulanov, 2014-07-22 20:51:20]

The CQ bit was checked by sergeyu@chromium.org

[Sergey Ulanov, 2014-07-22 20:52:52]

The CQ bit was checked by sergeyu@chromium.org

[commit-bot: I haz the power, 2014-07-22 20:54:28]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/sergeyu@chromium.org/394883008/130001

[commit-bot: I haz the power, 2014-07-22 21:40:52]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  android_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_clang_dbg/bui...)
  android_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_dbg/builds/20...)
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)
  ios_dbg_simulator on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_dbg_simulator/bui...)
  ios_rel_device on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device/builds...)
  ios_rel_device_ninja on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device_ninja/...)
  linux_chromium_chromeos_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)
  linux_chromium_chromeos_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)
  linux_chromium_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_clang_...)
  linux_chromium_rel_swarming on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_rel_sw...)
  mac_chromium_compile_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/mac_chromium_compile_...)
  mac_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/mac_chromium_rel/buil...)
  win8_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win8_chromium_rel/bui...)
  win_chromium_compile_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_compile_...)
  win_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_rel/buil...)
  win_chromium_x64_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_x64_rel/...)

[commit-bot: I haz the power, 2014-07-22 21:44:38]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-07-22 21:44:39]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)

[Sergey Ulanov, 2014-07-23 00:32:32]

The CQ bit was checked by sergeyu@chromium.org

[commit-bot: I haz the power, 2014-07-23 00:34:11]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/sergeyu@chromium.org/394883008/150001

[commit-bot: I haz the power, 2014-07-23 02:30:24]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  android_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_clang_dbg/bui...)
  android_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_dbg/builds/20...)
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)
  ios_dbg_simulator on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_dbg_simulator/bui...)
  ios_rel_device on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device/builds...)
  ios_rel_device_ninja on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device_ninja/...)
  linux_chromium_chromeos_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)
  linux_chromium_chromeos_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)
  linux_chromium_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_clang_...)
  linux_chromium_rel_swarming on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_rel_sw...)
  mac_chromium_compile_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/mac_chromium_compile_...)
  mac_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/mac_chromium_rel/buil...)
  win8_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win8_chromium_rel/bui...)
  win_chromium_compile_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_compile_...)
  win_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_rel/buil...)
  win_chromium_x64_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/win_chromium_x64_rel/...)

[commit-bot: I haz the power, 2014-07-23 02:34:42]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-07-23 02:34:43]

Try jobs failed on following builders:
  android_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_clang_dbg/bui...)
  android_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/android_dbg/builds/20...)
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)
  linux_chromium_chromeos_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)
  linux_chromium_chromeos_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)

[Sergey Ulanov, 2014-07-24 01:28:55]

The CQ bit was checked by sergeyu@chromium.org

[commit-bot: I haz the power, 2014-07-24 01:32:30]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/sergeyu@chromium.org/394883008/170001

[Sergey Ulanov, 2014-07-24 03:04:53]

The CQ bit was checked by sergeyu@chromium.org

[commit-bot: I haz the power, 2014-07-24 03:08:53]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/sergeyu@chromium.org/394883008/220001

[commit-bot: I haz the power, 2014-07-24 05:03:57]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)
  ios_dbg_simulator on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_dbg_simulator/bui...)
  ios_rel_device on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device/builds...)
  ios_rel_device_ninja on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device_ninja/...)
  linux_chromium_chromeos_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)
  linux_chromium_clang_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_clang_...)
  linux_chromium_rel_swarming on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_rel_sw...)
  mac_chromium_compile_dbg on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/mac_chromium_compile_...)
  mac_chromium_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/mac_chromium_rel/buil...)

[commit-bot: I haz the power, 2014-07-24 05:09:12]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-07-24 05:09:13]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/chromium_presubmit/bu...)
  ios_rel_device on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device/builds...)
  ios_rel_device_ninja on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/ios_rel_device_ninja/...)

[Sergey Ulanov, 2014-07-24 18:20:18]

+ttuttle in TBR for src/net in remoting/test/DEPS

[Sergey Ulanov, 2014-07-24 18:20:26]

The CQ bit was checked by sergeyu@chromium.org

[commit-bot: I haz the power, 2014-07-24 18:21:58]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/sergeyu@chromium.org/394883008/240001

[Deprecated (see juliatuttle), 2014-07-24 18:24:22]

On 2014/07/24 18:20:26, Sergey Ulanov wrote:
> The CQ bit was checked by mailto:sergeyu@chromium.org

lgtm, although I seem to be overlooking what in protocol_perftest.cc actually
depends on url_request_context_getter.h.

[Sergey Ulanov, 2014-07-24 20:11:20]

The CQ bit was checked by sergeyu@chromium.org

[commit-bot: I haz the power, 2014-07-24 20:13:39]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/sergeyu@chromium.org/394883008/260001

[commit-bot: I haz the power, 2014-07-24 23:57:48]

FYI, CQ is re-trying this CL (attempt #1).
The failing builders are:
  linux_chromium_chromeos_rel on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_chrome...)
  linux_chromium_rel_swarming on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_rel_sw...)

[commit-bot: I haz the power, 2014-07-25 00:38:38]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-07-25 00:38:39]

Try jobs failed on following builders:
  linux_chromium_rel_swarming on tryserver.chromium
(http://build.chromium.org/p/tryserver.chromium/builders/linux_chromium_rel_sw...)