In https://pinpoint-dot-chromeperf.appspot.com/job/177524c0140000
as well as in https://pinpoint-dot-chromeperf.appspot.com/job/16beaa50140000 the pinpoint jobs post on the bug: 

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/177524c0140000

But the benchmark execution failed with build failures.
"BuildError: Build failed: BUILD_FAILURE"

If I interpret this correctly, the pinpoint jobs seem to have attempted to bisect into a third_party/harfbuzz_ng roll, but then encountered commits with which we cannot build. 

However, I don't think a failed build is a meaningful identification of a performance difference and adds noise to the bug. I would suggest to change the pinpoint message to explain that the pinpoint jobs have failed.