Fix analyze in mb.py.

Fix analyze in mb.py.

As part of #466704, I changed some logic in mb.py to sort the inputs
that MB hands to GN, in an attempt to make the debugging output a
little easier to follow. It turns out that the way I did this was
broken, as there was a dependency on the ordering of the unsorted
values.

As a result, MB started remapping GN's analyze results back to the
wrong targets, and we've been running the wrong test steps since #466704
landed :(.

TBR=kbr@chromium.org, jam@chromium.org
BUG=714336
NOTRY=true

Review-Url: https://codereview.chromium.org/2843663002
Cr-Commit-Position: refs/heads/master@{#466828}
Committed: https://chromium.googlesource.com/chromium/src/+/b7b183fa716d3b18f69ebc18e290eb97d735f296

[Dirk Pranke, 2017-04-24 23:46:20]

The CQ bit was checked by dpranke@chromium.org

[commit-bot: I haz the power, 2017-04-24 23:46:46]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-04-24 23:50:19]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1493077580233930, "parent_rev":
"4efeddc9c45b938f1c89b16f68938b3d9c7a31fc", "commit_rev":
"b7b183fa716d3b18f69ebc18e290eb97d735f296"}

[commit-bot: I haz the power, 2017-04-24 23:50:33]

Description was changed from

==========
Fix analyze in mb.py.

As part of #466704, I changed some logic in mb.py to sort the inputs
that MB hands to GN, in an attempt to make the debugging output a
little easier to follow. It turns out that the way I did this was
broken, as there was a dependency on the ordering of the unsorted
values.

As a result, MB started remapping GN's analyze results back to the
wrong targets, and we've been running the wrong test steps since #466704
landed :(.

TBR=kbr@chromium.org, jam@chromium.org
BUG=714336
NOTRY=true
==========

to

==========
Fix analyze in mb.py.

As part of #466704, I changed some logic in mb.py to sort the inputs
that MB hands to GN, in an attempt to make the debugging output a
little easier to follow. It turns out that the way I did this was
broken, as there was a dependency on the ordering of the unsorted
values.

As a result, MB started remapping GN's analyze results back to the
wrong targets, and we've been running the wrong test steps since #466704
landed :(.

TBR=kbr@chromium.org, jam@chromium.org
BUG=714336
NOTRY=true

Review-Url: https://codereview.chromium.org/2843663002
Cr-Commit-Position: refs/heads/master@{#466828}
Committed:
https://chromium.googlesource.com/chromium/src/+/b7b183fa716d3b18f69ebc18e290...
==========

[commit-bot: I haz the power, 2017-04-24 23:50:34]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/b7b183fa716d3b18f69ebc18e290...