First failing build on peach_pit:
https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/peach_pit-tot-chrome-pfq-informational/builds/722

450871296 opt/google/chrome/chrome#new
ERROR   : Target image has run out of space:
ERROR   : Filesystem     1M-blocks  Used Available Use% Mounted on
ERROR   : /dev/loop0          1205  1205         0 100% /mnt/host/source/src/build/images/peach_pit/R51-8047.0.0-a1/rootfs
INFO    : Unmounting image from /mnt/host/source/src/build/images/peach_pit/R51-8047.0.0-a1/stateful and /mnt/host/source/src/build/images/peach_pit/R51-8047.0.0-a1/rootfs

Suspicious CL: https://chromium-review.googlesource.com/#/c/332061/

That change is only for testing Android/Brillo devices, shouldn't cause build failure.

There's an earlier error. Not sure if this means that chrome is too big, or if the builder ran out of space.

chromeos-chrome-51.0.2674.0_alpha-r1: !!! copy /build/peach_pit/tmp/portage/chromeos-base/chromeos-chrome-51.0.2674.0_alpha-r1/image/opt/google/chrome/chrome -> /mnt/host/source/src/build/images/peach_pit/R51-8047.0.0-a1/rootfs/opt/google/chrome/chrome failed.
chromeos-chrome-51.0.2674.0_alpha-r1: !!! [Errno 28] No space left on device
chromeos-chrome-51.0.2674.0_alpha-r1: >>> Failed to install chromeos-base/chromeos-chrome-51.0.2674.0_alpha-r1 to /mnt/host/source/src/build/images/peach_pit/R51-8047.0.0-a1/rootfs/, Log file:

Vincent, Kevin - do you know what may be going on here? Seems to be a cros build issue.

Need to repartition  the file system? Not sure. 

davidjames - do you know how we can tell if this build was already close to the 1.2GB limit and the limit just needs to be bumped up a little bit, or if something suddenly and unexpectedly caused it to jump past the limit?

This has now hit our actual (not just informational / TOT) pfq builders, eg:

https://uberchromegw.corp.google.com/i/chromeos/builders/peach_pit-chrome-pfq/builds/1801
https://uberchromegw.corp.google.com/i/chromeos/builders/daisy_skate-chrome-pfq/builds/2152
https://uberchromegw.corp.google.com/i/chromeos/builders/veyron_pinky-chrome-pfq/builds/2016

chromeos-chrome-51.0.2674.3_rc-r1:  [ ok ]
chromeos-chrome-51.0.2674.3_rc-r1:  * >>> SetUID: [chmod go-r] /opt/google/chrome/chrome-sandbox ...
chromeos-chrome-51.0.2674.3_rc-r1:  [ ok ]
chromeos-chrome-51.0.2674.3_rc-r1: !!! copy /build/veyron_pinky/tmp/portage/chromeos-base/chromeos-chrome-51.0.2674.3_rc-r1/image/opt/google/chrome/chrome -> /mnt/host/source/src/build/images/veyron_pinky/R51-8052.0.0-rc1/rootfs/opt/google/chrome/chrome failed.
chromeos-chrome-51.0.2674.3_rc-r1: !!! [Errno 28] No space left on device

BuildImages succeeds on these builders now.

Looks like this is happening again, can you please have another look?

https://uberchromegw.corp.google.com/i/chromeos/builders/daisy_skate-chrome-pfq/builds/2176/steps/BuildImage/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/nyan-chrome-pfq/builds/1063/steps/BuildImage/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/peach_pit-chrome-pfq/builds/1825/steps/BuildImage/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/veyron_pinky-chrome-pfq/builds/2040/steps/BuildImage/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/x86-alex-chrome-pfq/builds/371/steps/BuildImage/logs/stdio

I'm attempting to bisect now.

BTW, this looks like the Chrome binary size jumping to 300 MB again.

The current BuildImage failures are actually this: issue 595763

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/863d4ac7ebdcc83285329310c3d94cbe176841e0

commit 863d4ac7ebdcc83285329310c3d94cbe176841e0
Author: xdai <xdai@chromium.org>
Date: Thu Mar 17 22:21:43 2016

Revert of Re-land: Enable XFA-Forms for the PDFium plugin. (patchset #1 id:1 of https://codereview.chromium.org/1811743002/ )

Reason for revert:
Causing "Target image has run out of space" errors on Chrome OS builders:

http://crbug.com/595763

Original issue's description:
> Re-land: Enable XFA-Forms for the PDFium plugin.
>
> This reverts commit 13fe4645b7199ed2da4f1810d4c96262eaecea5f.
> See https://codereview.chromium.org/1761673002/
>
> TBR=thakis@chromium.org
>
> Committed: https://crrev.com/ed07b3773e3aad4a44a79a48c17162ef57ca82ee
> Cr-Commit-Position: refs/heads/master@{#381573}

TBR=thakis@chromium.org,ochang@chromium.org,jschuh@chromium.org,rpop@chromium.org,dsinclair@chromium.org,tsepez@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true

Review URL: https://codereview.chromium.org/1814843003

Cr-Commit-Position: refs/heads/master@{#381764}
(cherry picked from commit 7812fb8ba8271fbc542fd5716498517b82ba821a)

BUG=595763,  593969 

Review URL: https://codereview.chromium.org/1815003002 .

Cr-Commit-Position: refs/branch-heads/2681@{#7}
Cr-Branched-From: 2668bea689fd4a5ce07011903bca095aaf67bb07-refs/heads/master@{#381614}

[modify] https://crrev.com/863d4ac7ebdcc83285329310c3d94cbe176841e0/build/common.gypi

Merging into 595763 which tracks the main effort

Actually these are separate bugs

Bulk verified