Revert of [Devil] Replace generated Devil config with jinja template.

Revert of [Devil] Replace generated Devil config with jinja template. (patchset #8 id:140001 of https://codereview.chromium.org/1812383003/ )

Reason for revert:
I believe this change breaks content_browsertests on every Android tester in chromium.android.

Examples:

https://build.chromium.org/p/chromium.android/builders/Lollipop%20Phone%20Tester/builds/4031
https://build.chromium.org/p/chromium.android/builders/Marshmallow%2064%20bit%20Tester/builds/1457
https://build.chromium.org/p/chromium.android/builders/KitKat%20Tablet%20Tester/builds/3759

Original issue's description:
> [Devil] Replace generated Devil config with jinja template.
>
> This change will hopefully allow us to configure devil more based
> on the build config. For example, it will let us use the same
> android_sdk_tools to run tests that we use to build with.
>
> BUG=
>
> Committed: https://crrev.com/c2aa4243a9e00a2d0e254d9f6f73b41c00cb644d
> Cr-Commit-Position: refs/heads/master@{#386461}

TBR=droger@chromium.org,jbudorick@chromium.org,mikecase@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=

Committed: https://crrev.com/d408713145a9b75e155e1bf106105803ad40b1bd
Cr-Commit-Position: refs/heads/master@{#386648}

[kjellander_chromium, 2016-04-12 10:57:47]

Created Revert of [Devil] Replace generated Devil config with jinja template.

[commit-bot: I haz the power, 2016-04-12 10:57:59]

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

[commit-bot: I haz the power, 2016-04-12 10:58:34]

Description was changed from

==========
Revert of [Devil] Replace generated Devil config with jinja template. (patchset
#8 id:140001 of https://codereview.chromium.org/1812383003/ )

Reason for revert:
I believe this change breaks content_browsertests on every Android tester in
chromium.android. 

Examples:

https://build.chromium.org/p/chromium.android/builders/Lollipop%20Phone%20Tes...
https://build.chromium.org/p/chromium.android/builders/Marshmallow%2064%20bit...
https://build.chromium.org/p/chromium.android/builders/KitKat%20Tablet%20Test...

Original issue's description:
> [Devil] Replace generated Devil config with jinja template.
> 
> This change will hopefully allow us to configure devil more based
> on the build config. For example, it will let us use the same
> android_sdk_tools to run tests that we use to build with.
> 
> BUG=
> 
> Committed: https://crrev.com/c2aa4243a9e00a2d0e254d9f6f73b41c00cb644d
> Cr-Commit-Position: refs/heads/master@{#386461}

TBR=droger@chromium.org,jbudorick@chromium.org,mikecase@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=
==========

to

==========
Revert of [Devil] Replace generated Devil config with jinja template. (patchset
#8 id:140001 of https://codereview.chromium.org/1812383003/ )

Reason for revert:
I believe this change breaks content_browsertests on every Android tester in
chromium.android. 

Examples:

https://build.chromium.org/p/chromium.android/builders/Lollipop%20Phone%20Tes...
https://build.chromium.org/p/chromium.android/builders/Marshmallow%2064%20bit...
https://build.chromium.org/p/chromium.android/builders/KitKat%20Tablet%20Test...

Original issue's description:
> [Devil] Replace generated Devil config with jinja template.
> 
> This change will hopefully allow us to configure devil more based
> on the build config. For example, it will let us use the same
> android_sdk_tools to run tests that we use to build with.
> 
> BUG=
> 
> Committed: https://crrev.com/c2aa4243a9e00a2d0e254d9f6f73b41c00cb644d
> Cr-Commit-Position: refs/heads/master@{#386461}

TBR=droger@chromium.org,jbudorick@chromium.org,mikecase@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=
==========

[commit-bot: I haz the power, 2016-04-12 10:58:35]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-04-12 11:00:26]

Description was changed from

==========
Revert of [Devil] Replace generated Devil config with jinja template. (patchset
#8 id:140001 of https://codereview.chromium.org/1812383003/ )

Reason for revert:
I believe this change breaks content_browsertests on every Android tester in
chromium.android. 

Examples:

https://build.chromium.org/p/chromium.android/builders/Lollipop%20Phone%20Tes...
https://build.chromium.org/p/chromium.android/builders/Marshmallow%2064%20bit...
https://build.chromium.org/p/chromium.android/builders/KitKat%20Tablet%20Test...

Original issue's description:
> [Devil] Replace generated Devil config with jinja template.
> 
> This change will hopefully allow us to configure devil more based
> on the build config. For example, it will let us use the same
> android_sdk_tools to run tests that we use to build with.
> 
> BUG=
> 
> Committed: https://crrev.com/c2aa4243a9e00a2d0e254d9f6f73b41c00cb644d
> Cr-Commit-Position: refs/heads/master@{#386461}

TBR=droger@chromium.org,jbudorick@chromium.org,mikecase@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=
==========

to

==========
Revert of [Devil] Replace generated Devil config with jinja template. (patchset
#8 id:140001 of https://codereview.chromium.org/1812383003/ )

Reason for revert:
I believe this change breaks content_browsertests on every Android tester in
chromium.android.

Examples:

https://build.chromium.org/p/chromium.android/builders/Lollipop%20Phone%20Tes...
https://build.chromium.org/p/chromium.android/builders/Marshmallow%2064%20bit...
https://build.chromium.org/p/chromium.android/builders/KitKat%20Tablet%20Test...

Original issue's description:
> [Devil] Replace generated Devil config with jinja template.
>
> This change will hopefully allow us to configure devil more based
> on the build config. For example, it will let us use the same
> android_sdk_tools to run tests that we use to build with.
>
> BUG=
>
> Committed: https://crrev.com/c2aa4243a9e00a2d0e254d9f6f73b41c00cb644d
> Cr-Commit-Position: refs/heads/master@{#386461}

TBR=droger@chromium.org,jbudorick@chromium.org,mikecase@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=

Committed: https://crrev.com/d408713145a9b75e155e1bf106105803ad40b1bd
Cr-Commit-Position: refs/heads/master@{#386648}
==========

[commit-bot: I haz the power, 2016-04-12 11:00:27]

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

[kjellander_chromium, 2016-04-12 12:17:43]

On 2016/04/12 11:00:27, commit-bot: I haz the power wrote:
> Patchset 1 (id:??) landed as
> https://crrev.com/d408713145a9b75e155e1bf106105803ad40b1bd
> Cr-Commit-Position: refs/heads/master@{#386648}

I can confirm that all the bots in
https://build.chromium.org/p/chromium.webrtc.fyi/waterfall are now green.
I filed https://bugs.chromium.org/p/chromium/issues/detail?id=602608 to ask why
these errors didn't show up in sheriff-o-matic.