Fix instrumented libraries sha1 mix-up.

Fix instrumented libraries sha1 mix-up.

Fix an unexplainable confusion in the prebuilt instrumented libraries
sha1 identifiers: no-origins-trusty has sha1 that actually belongs to
chained-origins trusty, and vice versa.

This can never cause a hard failure, but sometimes with-origins build
may miss origin information, and, in all cases (we actually see this
in clusterfuzz reports) no-origins build prints
  ORIGIN: invalid(0)
at the end of the MSan report.

R=hans@chromium.org
BUG=590867
NOTRY=true

Committed: https://crrev.com/2a28406877d06cc4d7511295067c6be031e70e9d
Cr-Commit-Position: refs/heads/master@{#378309}

[eugenis, 2016-02-29 22:50:46]

Description was changed from

==========
Fix instrumented libraries sha1 mix-up.

Fix an unexplainable confusion in the prebuilt instrumented libraries
sha1 identifiers: no-origins-trusty has sha1 that actually belongs to
chained-origins trusty, and vice versa.

This can never cause a hard failure, but sometimes with-origins build
may miss origin information, and, in all cases (we actually see this
in clusterfuzz reports) no-origins build prints
  ORIGIN: invalid(0)
at the end of the MSan report.

R=hans@chromium.org
BUGS=590867
BUG=
==========

to

==========
Fix instrumented libraries sha1 mix-up.

Fix an unexplainable confusion in the prebuilt instrumented libraries
sha1 identifiers: no-origins-trusty has sha1 that actually belongs to
chained-origins trusty, and vice versa.

This can never cause a hard failure, but sometimes with-origins build
may miss origin information, and, in all cases (we actually see this
in clusterfuzz reports) no-origins build prints
  ORIGIN: invalid(0)
at the end of the MSan report.

R=hans@chromium.org
BUG=590867
==========

[eugenis, 2016-02-29 22:51:54]

Description was changed from

==========
Fix instrumented libraries sha1 mix-up.

Fix an unexplainable confusion in the prebuilt instrumented libraries
sha1 identifiers: no-origins-trusty has sha1 that actually belongs to
chained-origins trusty, and vice versa.

This can never cause a hard failure, but sometimes with-origins build
may miss origin information, and, in all cases (we actually see this
in clusterfuzz reports) no-origins build prints
  ORIGIN: invalid(0)
at the end of the MSan report.

R=hans@chromium.org
BUG=590867
==========

to

==========
Fix instrumented libraries sha1 mix-up.

Fix an unexplainable confusion in the prebuilt instrumented libraries
sha1 identifiers: no-origins-trusty has sha1 that actually belongs to
chained-origins trusty, and vice versa.

This can never cause a hard failure, but sometimes with-origins build
may miss origin information, and, in all cases (we actually see this
in clusterfuzz reports) no-origins build prints
  ORIGIN: invalid(0)
at the end of the MSan report.

R=hans@chromium.org
BUG=590867
NOTRY=true
==========

[hans, 2016-02-29 22:55:46]

rs-lgtm

[Evgeniy Stepanov, 2016-02-29 22:57:51]

The CQ bit was checked by eugenis@google.com

[commit-bot: I haz the power, 2016-02-29 22:58:55]

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

[commit-bot: I haz the power, 2016-02-29 23:11:41]

Description was changed from

==========
Fix instrumented libraries sha1 mix-up.

Fix an unexplainable confusion in the prebuilt instrumented libraries
sha1 identifiers: no-origins-trusty has sha1 that actually belongs to
chained-origins trusty, and vice versa.

This can never cause a hard failure, but sometimes with-origins build
may miss origin information, and, in all cases (we actually see this
in clusterfuzz reports) no-origins build prints
  ORIGIN: invalid(0)
at the end of the MSan report.

R=hans@chromium.org
BUG=590867
NOTRY=true
==========

to

==========
Fix instrumented libraries sha1 mix-up.

Fix an unexplainable confusion in the prebuilt instrumented libraries
sha1 identifiers: no-origins-trusty has sha1 that actually belongs to
chained-origins trusty, and vice versa.

This can never cause a hard failure, but sometimes with-origins build
may miss origin information, and, in all cases (we actually see this
in clusterfuzz reports) no-origins build prints
  ORIGIN: invalid(0)
at the end of the MSan report.

R=hans@chromium.org
BUG=590867
NOTRY=true
==========

[commit-bot: I haz the power, 2016-02-29 23:11:42]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-02-29 23:13:57]

Description was changed from

==========
Fix instrumented libraries sha1 mix-up.

Fix an unexplainable confusion in the prebuilt instrumented libraries
sha1 identifiers: no-origins-trusty has sha1 that actually belongs to
chained-origins trusty, and vice versa.

This can never cause a hard failure, but sometimes with-origins build
may miss origin information, and, in all cases (we actually see this
in clusterfuzz reports) no-origins build prints
  ORIGIN: invalid(0)
at the end of the MSan report.

R=hans@chromium.org
BUG=590867
NOTRY=true
==========

to

==========
Fix instrumented libraries sha1 mix-up.

Fix an unexplainable confusion in the prebuilt instrumented libraries
sha1 identifiers: no-origins-trusty has sha1 that actually belongs to
chained-origins trusty, and vice versa.

This can never cause a hard failure, but sometimes with-origins build
may miss origin information, and, in all cases (we actually see this
in clusterfuzz reports) no-origins build prints
  ORIGIN: invalid(0)
at the end of the MSan report.

R=hans@chromium.org
BUG=590867
NOTRY=true

Committed: https://crrev.com/2a28406877d06cc4d7511295067c6be031e70e9d
Cr-Commit-Position: refs/heads/master@{#378309}
==========

[commit-bot: I haz the power, 2016-02-29 23:13:57]

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