Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of sullivan@google.com

sizes failing on multiple builders

Builders failed on: 
- linux-builder-perf: 
  https://ci.chromium.org/p/chrome/builders/luci.chrome.ci/linux-builder-perf
- mac-builder-perf: 
  https://ci.chromium.org/p/chrome/builders/luci.chrome.ci/mac-builder-perf

First failed builds:
https://ci.chromium.org/p/chrome/builders/luci.chrome.ci/mac-builder-perf/14345
https://ci.chromium.org/p/chrome/builders/luci.chrome.ci/linux-builder-perf/14643

Both have the same pdfium roll as the culprit: r600186:

https://pdfium.googlesource.com/pdfium.git/+log/c3da36973048..2894645e6c18


git log c3da36973048..2894645e6c18 --date=short --no-merges --format='%ad %ae %s'
2018-10-16 thestig@chromium.org Add FxFileCloser for scoped FILE* closing.
2018-10-16 thestig@chromium.org Use PartitionAllocZeroFill in FX_SafeAlloc().
2018-10-16 thestig@chromium.org Make some third_party targets pass gn check.
2018-10-16 thestig@chromium.org Make skia/ pass gn check.
2018-10-16 thestig@chromium.org Use PartitionAllocZeroFill in CFX_V8ArrayBufferAllocator::Allocate().
2018-10-16 thestig@chromium.org Update PartitionAlloc from Chromium at r599712.
2018-10-16 thestig@chromium.org Make constants/ pass gn check.

thestig: any ideas if the pdfium roll could have caused this failure?

Apologies if I'm blind, but I can't find the actual source of the error in stdout:
https://logs.chromium.org/logs/chrome/buildbucket/cr-buildbucket.appspot.com/8932465673126990144/+/steps/sizes/0/stdout

I just see this at the bottom:
exit code (as seen by runtest.py): 125
Sending result 2 of 2 to dashboard.
step returned non-zero exit code: 125