Remove the 'compile_targets' from 'Linux x64' on the chromium waterfall.

Remove the 'compile_targets' from 'Linux x64' on the chromium waterfall.

The bot was previously specifying 'all' in compile_targets,
which was getting added on to values specified in the src-side
//testing/buildbot file, making it impossible to have the bot
build anything other than all (i.e., to switch it to 'gn_all').
Since the src-side file also specifies 'all' at the moment,
this is worse than redundant.

TBR=phajdan.jr@chromium.org
BUG=545480, 432959
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=297634

[Dirk Pranke, 2015-11-20 02:27:14]

https://codereview.chromium.org/1466563002/diff/1/scripts/slave/recipes/chrom...
File
scripts/slave/recipes/chromium_trybot.expected/full_tryserver_chromium_linux_linux_chromium_archive_rel_ng.json
(right):

https://codereview.chromium.org/1466563002/diff/1/scripts/slave/recipes/chrom...
scripts/slave/recipes/chromium_trybot.expected/full_tryserver_chromium_linux_linux_chromium_archive_rel_ng.json:204:
"@@@STEP_LOG_LINE@analyze_details@  \"self.m.filter.compile_targets\": [], @@@",
I'm not sure why this is using [] instead of ["All", "chromium_builder_tests"].
Maybe a problem with the step test data?

[Dirk Pranke, 2015-11-20 02:27:17]

The CQ bit was checked by dpranke@chromium.org

[commit-bot: I haz the power, 2015-11-20 02:27:27]

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

[commit-bot: I haz the power, 2015-11-20 02:30:26]

Committed patchset #1 (id:1) as
http://src.chromium.org/viewvc/chrome?view=rev&revision=297634