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
at the end of the MSan report.
Review URL: https://codereview.chromium.org/1751643002
2 files changed