Convert sandbox_linux_unittests to run exclusively on Swarming

Convert sandbox_linux_unittests to run exclusively on Swarming

0 configs already ran on Swarming
16 used to run locally and were converted:
- chromium.chromiumos.json: Linux ChromiumOS Ozone Tests (1)
- chromium.chromiumos.json: Linux ChromiumOS Tests (1)
- chromium.chromiumos.json: Linux ChromiumOS Tests (dbg)(1)
- chromium.fyi.json: Linux Trusty
- chromium.fyi.json: Linux Trusty (dbg)
- chromium.linux.json: Cast Linux
- chromium.linux.json: Linux Tests
- chromium.linux.json: Linux Tests (dbg)(1)
- chromium.linux.json: Linux Tests (dbg)(1)(32)
- chromium.memory.fyi.json: Linux ChromeOS MSan Tests
- chromium.memory.fyi.json: Linux MSan Tests
- chromium.memory.fyi.json: Linux TSan Tests
- chromium.memory.json: Linux ASan LSan Tests (1)
- chromium.memory.json: Linux Chromium OS ASan LSan Tests (1)
- chromium.webkit.json: Linux ChromiumOS Tests (1)
- chromium.webkit.json: Linux ChromiumOS Tests (dbg)(1)

Ran:
  ./manage.py --convert sandbox_linux_unittests

R=jln@chromium.org,dpranke@chromium.org
TBR=
BUG=98637
Committed: https://crrev.com/48b930f48413e09c62fdb8dc6f5167b00876c5c9
Cr-Commit-Position: refs/heads/master@{#336873}

[M-A Ruel, 2015-06-30 21:01:06]

TBR'ing since it's a mechanical change.

[M-A Ruel, 2015-06-30 21:01:11]

The CQ bit was checked by maruel@chromium.org

[commit-bot: I haz the power, 2015-06-30 21:01:54]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1215213002/1

[commit-bot: I haz the power, 2015-06-30 21:09:18]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-06-30 21:10:30]

Patchset 1 (id:??) landed as
https://crrev.com/48b930f48413e09c62fdb8dc6f5167b00876c5c9
Cr-Commit-Position: refs/heads/master@{#336873}

[jln (very slow on Chromium), 2015-06-30 23:49:57]

Wasn't there an issue with this breaking on Android because it starts running
thread with the new modern framework which unfortunately starts threads?

[M-A Ruel, 2015-07-01 00:03:24]

On 2015/06/30 23:49:57, jln wrote:
> Wasn't there an issue with this breaking on Android because it starts running
> thread with the new modern framework which unfortunately starts threads?

This change didn't affect any Android builder.

[Dirk Pranke, 2015-07-01 19:58:04]

lgtm