Agree. I think it may be historical - originally we just did the perf bot stuff and that implementation went in first. Then, when we backed them in, I think we just didn't convert the perf ones.

I think getting rid of the duplicate config parsing code in the perf infrastructure would be a good outcome, assuming we make them use the baked-in configs. One thing we should be careful with is if the perf bots test official builds - because by default official builds don't use the baked in configs.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/1c70046ee9bfd7f0159b3408331e26b9f61ef49f

commit 1c70046ee9bfd7f0159b3408331e26b9f61ef49f
Author: robliao <robliao@chromium.org>
Date: Tue Sep 27 23:37:55 2016

Update fieldtrial_util To Handle Combined Fieldtrial Config Format

BUG=649363, 650705

Review-Url: https://codereview.chromium.org/2373843002
Cr-Commit-Position: refs/heads/master@{#421384}

[modify] https://crrev.com/1c70046ee9bfd7f0159b3408331e26b9f61ef49f/tools/perf/BUILD.gn
[modify] https://crrev.com/1c70046ee9bfd7f0159b3408331e26b9f61ef49f/tools/perf/core/perf_benchmark.py
[modify] https://crrev.com/1c70046ee9bfd7f0159b3408331e26b9f61ef49f/tools/variations/fieldtrial_to_struct.py
[modify] https://crrev.com/1c70046ee9bfd7f0159b3408331e26b9f61ef49f/tools/variations/fieldtrial_util.py
[modify] https://crrev.com/1c70046ee9bfd7f0159b3408331e26b9f61ef49f/tools/variations/fieldtrial_util_unittest.py

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/420af6678ef6a2cff2e34abf62f3b5b0cc83ee7a

commit 420af6678ef6a2cff2e34abf62f3b5b0cc83ee7a
Author: robliao <robliao@chromium.org>
Date: Wed Sep 28 19:48:11 2016

Remove Extra Underscore

BUG=649363, 650705

Review-Url: https://codereview.chromium.org/2378153002
Cr-Commit-Position: refs/heads/master@{#421611}

[modify] https://crrev.com/420af6678ef6a2cff2e34abf62f3b5b0cc83ee7a/tools/perf/core/perf_benchmark.py

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/8a36a0b62259e09607485d26180e19a0e418c99f

commit 8a36a0b62259e09607485d26180e19a0e418c99f
Author: robliao <robliao@chromium.org>
Date: Wed Sep 28 20:37:00 2016

Revert of Remove Extra Underscore (patchset #1 id:1 of https://codereview.chromium.org/2378153002/ )

Reason for revert:
Reverting to prepare for revert of
https://codereview.chromium.org/2373843002/

due to
https://build.chromium.org/p/chromiumos.chromium/builders/amd64-generic-telemetry/builds/9845

Original issue's description:
> Remove Extra Underscore
>
> BUG=649363, 650705
>
> Committed: https://crrev.com/420af6678ef6a2cff2e34abf62f3b5b0cc83ee7a
> Cr-Commit-Position: refs/heads/master@{#421611}

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

Review-Url: https://codereview.chromium.org/2381653002
Cr-Commit-Position: refs/heads/master@{#421631}

[modify] https://crrev.com/8a36a0b62259e09607485d26180e19a0e418c99f/tools/perf/core/perf_benchmark.py

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/cf6e4a4caebe29f7f794bb5775d5d9f03e5e4dcb

commit cf6e4a4caebe29f7f794bb5775d5d9f03e5e4dcb
Author: robliao <robliao@chromium.org>
Date: Wed Sep 28 20:39:20 2016

Revert of Update fieldtrial_util To Handle Combined Fieldtrial Config Format (patchset #4 id:80001 of https://codereview.chromium.org/2373843002/ )

Reason for revert:
Break in
https://build.chromium.org/p/chromiumos.chromium/builders/amd64-generic-telemetry/builds/9845

This isn't part of the CQ run it appears.

Original issue's description:
> Update fieldtrial_util To Handle Combined Fieldtrial Config Format
>
> BUG=649363, 650705
>
> Committed: https://crrev.com/1c70046ee9bfd7f0159b3408331e26b9f61ef49f
> Cr-Commit-Position: refs/heads/master@{#421384}

TBR=aiolos@chromium.org,asvitkine@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=649363, 650705

Review-Url: https://codereview.chromium.org/2381663002
Cr-Commit-Position: refs/heads/master@{#421632}

[modify] https://crrev.com/cf6e4a4caebe29f7f794bb5775d5d9f03e5e4dcb/tools/perf/BUILD.gn
[modify] https://crrev.com/cf6e4a4caebe29f7f794bb5775d5d9f03e5e4dcb/tools/perf/core/perf_benchmark.py
[modify] https://crrev.com/cf6e4a4caebe29f7f794bb5775d5d9f03e5e4dcb/tools/variations/fieldtrial_to_struct.py
[modify] https://crrev.com/cf6e4a4caebe29f7f794bb5775d5d9f03e5e4dcb/tools/variations/fieldtrial_util.py
[modify] https://crrev.com/cf6e4a4caebe29f7f794bb5775d5d9f03e5e4dcb/tools/variations/fieldtrial_util_unittest.py

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/8da8200a279fcafc4a7c68f2e6ef95f4d721bb3a

commit 8da8200a279fcafc4a7c68f2e6ef95f4d721bb3a
Author: robliao <robliao@chromium.org>
Date: Wed Sep 28 22:47:31 2016

Update fieldtrial_util To Handle Combined Fieldtrial Config Format

BUG=649363, 650705

Review-Url: https://codereview.chromium.org/2373843002
Cr-Commit-Position: refs/heads/master@{#421670}

[modify] https://crrev.com/8da8200a279fcafc4a7c68f2e6ef95f4d721bb3a/tools/perf/BUILD.gn
[modify] https://crrev.com/8da8200a279fcafc4a7c68f2e6ef95f4d721bb3a/tools/perf/bootstrap_deps
[modify] https://crrev.com/8da8200a279fcafc4a7c68f2e6ef95f4d721bb3a/tools/perf/core/perf_benchmark.py
[modify] https://crrev.com/8da8200a279fcafc4a7c68f2e6ef95f4d721bb3a/tools/variations/fieldtrial_to_struct.py
[modify] https://crrev.com/8da8200a279fcafc4a7c68f2e6ef95f4d721bb3a/tools/variations/fieldtrial_util.py
[modify] https://crrev.com/8da8200a279fcafc4a7c68f2e6ef95f4d721bb3a/tools/variations/fieldtrial_util_unittest.py

Hey Robliao - what outstanding work is there for this bug? Can we close it out?

The main question here is if
https://cs.chromium.org/chromium/src/tools/variations/fieldtrial_util.py
should even exist at all.

Perfbots rely on command line args to determine the default state of their fieldtrials. It would be better if they could directly reference the fieldtrials instead of going through args.

It's unlikely I'm going to get to this soon, so marking as available.
Setting as Pri-3 as it's not urgent.