yeah, i don't think this was finished being set up

i would guess the cbuildbot config is missing sync_chrome=True

over to Phillip who worked on setting this up initially

vapier: Can you link to an example where this is set, or docs describing it? 

the same place where all the other changes Philip made ...
  https://chromium-review.googlesource.com/1142352

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/73c52b53956d9f9508e5a14ba81d4046137e74c1

commit 73c52b53956d9f9508e5a14ba81d4046137e74c1
Author: Nick Sanders <nsanders@chromium.org>
Date: Sat Aug 11 01:57:59 2018

cbuildbot_config: enable sync chrome for factory

We need the Chrome source on factory branches to build Chrome.

BUG=chromium:863652
TEST=None

Change-Id: I3206283580720d0a8503e368f133239ea764b8f3
Reviewed-on: https://chromium-review.googlesource.com/1171910
Reviewed-by: Nick Sanders <nsanders@chromium.org>
Commit-Queue: Nick Sanders <nsanders@chromium.org>
Tested-by: Nick Sanders <nsanders@chromium.org>

[modify] https://crrev.com/73c52b53956d9f9508e5a14ba81d4046137e74c1/cbuildbot/config_dump.json
[modify] https://crrev.com/73c52b53956d9f9508e5a14ba81d4046137e74c1/cbuildbot/chromeos_config.py

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/5e00d17a508a2beb2d0f2f97903c6228f47ae42f

commit 5e00d17a508a2beb2d0f2f97903c6228f47ae42f
Author: Nick Sanders <nsanders@chromium.org>
Date: Tue Aug 14 02:02:38 2018

scarlet pre-flight: match with soraka config

No idea what this does but soraka is working so lets copy that.

BUG=chromium:863652
TEST=None

Change-Id: I4290df0ea932dc536bde1500009e2abbcab5f848
Reviewed-on: https://chromium-review.googlesource.com/1173735
Reviewed-by: Nick Sanders <nsanders@chromium.org>
Commit-Queue: Nick Sanders <nsanders@chromium.org>
Tested-by: Nick Sanders <nsanders@chromium.org>

[modify] https://crrev.com/5e00d17a508a2beb2d0f2f97903c6228f47ae42f/cbuildbot/config_dump.json
[modify] https://crrev.com/5e00d17a508a2beb2d0f2f97903c6228f47ae42f/cbuildbot/chromeos_config.py

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/6b0ee18a34566a44a3acb3377b8b4581683d73ed

commit 6b0ee18a34566a44a3acb3377b8b4581683d73ed
Author: Nick Sanders <nsanders@chromium.org>
Date: Tue Aug 14 03:22:08 2018

chrome: make chrome "sticky"

Because apparently lack of stickiness is a thing that breaks infra?

BUG=chromium:863652
TEST=None

Change-Id: I87c10fc79f234a4fc483724fc9a4644ccf5ca238
Reviewed-on: https://chromium-review.googlesource.com/1173757
Reviewed-by: Nick Sanders <nsanders@chromium.org>
Commit-Queue: Nick Sanders <nsanders@chromium.org>
Tested-by: Nick Sanders <nsanders@chromium.org>

[add] https://crrev.com/6b0ee18a34566a44a3acb3377b8b4581683d73ed/chromeos-base/chromeos-chrome/chromeos-chrome-65.0.3293.0-r1.ebuild

https://logs.chromium.org/v/?s=chromeos%2Fbb%2Fchromeos.branch%2Fscarlet_pre-flight_factory-scarlet-10211.B%2F69%2F%2B%2Frecipes%2Fsteps%2FBuildImage%2F0%2Fstdout

Currently failing with:
chromeos-chrome-65.0.3311.0_rc-r1: !!! [Errno 28] No space left on device

May be a builder issue? 

out of space errors are never a problem with the builder.  it's always a problem with the image not being big enough for all the content trying to be installed into it.

you can either increase the image size (through baseboard-gru/scripts/disk_layout.json) or try to remove files.

just increasing the rootfs size is probably the easiest way forward.

Sorry, I didn't see the issue assigned to me until now.
It looks like my chromium-auto-forward is disabled.

It never works right to begin with, so I've been kicking off factory build manually for scarlet.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/795430b025399da5420cd1c90f3fb51083be9332

commit 795430b025399da5420cd1c90f3fb51083be9332
Author: Nick Sanders <nsanders@chromium.org>
Date: Tue Aug 14 22:56:02 2018

scarlet: chrome: make stickly again

repo provides stale branch data, updating CL with the
actual branch data.

BUG=chromium:863652
TEST=None

Change-Id: I3a4368f1570d688cbea7b27dc5736eced8939c49
Reviewed-on: https://chromium-review.googlesource.com/1175224
Reviewed-by: Nick Sanders <nsanders@chromium.org>
Commit-Queue: Nick Sanders <nsanders@chromium.org>
Tested-by: Nick Sanders <nsanders@chromium.org>

[delete] https://crrev.com/c943784b25a6b0e529569945a01fe490fe0a68ee/chromeos-base/chromeos-chrome/chromeos-chrome-65.0.3293.0-r1.ebuild
[rename] https://crrev.com/795430b025399da5420cd1c90f3fb51083be9332/chromeos-base/chromeos-chrome/chromeos-chrome-65.0.3311.0-r1.ebuild

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/c7919116be35a1f3ff1952262a2dfee2b6f689eb

commit c7919116be35a1f3ff1952262a2dfee2b6f689eb
Author: Nick Sanders <nsanders@chromium.org>
Date: Tue Aug 14 22:59:27 2018

scarlet: enlarge rootfs to 1.8G

Somehow it's full without any changes.

BUG=chromium:863652
TEST=None

Change-Id: I488f8b5780364486f590d9c8e1bdc7271d4fc2ea
Reviewed-on: https://chromium-review.googlesource.com/1175204
Reviewed-by: Nick Sanders <nsanders@chromium.org>
Commit-Queue: Nick Sanders <nsanders@chromium.org>
Tested-by: Nick Sanders <nsanders@chromium.org>

[modify] https://crrev.com/c7919116be35a1f3ff1952262a2dfee2b6f689eb/baseboard-gru/scripts/disk_layout.json

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/c02b8e7253f3d1a711e136a1d47ae347e87ceba3

commit c02b8e7253f3d1a711e136a1d47ae347e87ceba3
Author: Nick Sanders <nsanders@chromium.org>
Date: Thu Aug 16 01:51:30 2018

Revert "scarlet pre-flight: match with soraka config"

This reverts commit 5e00d17a508a2beb2d0f2f97903c6228f47ae42f.

Reason for revert: didn't fix the build

Original change's description:
> scarlet pre-flight: match with soraka config
> 
> No idea what this does but soraka is working so lets copy that.
> 
> BUG=chromium:863652
> TEST=None
> 
> Change-Id: I4290df0ea932dc536bde1500009e2abbcab5f848
> Reviewed-on: https://chromium-review.googlesource.com/1173735
> Reviewed-by: Nick Sanders <nsanders@chromium.org>
> Commit-Queue: Nick Sanders <nsanders@chromium.org>
> Tested-by: Nick Sanders <nsanders@chromium.org>

Bug: chromium:863652
Change-Id: I3f531ba439a67d2b3caaf416368365488125de6e
Reviewed-on: https://chromium-review.googlesource.com/1176941
Reviewed-by: Nick Sanders <nsanders@chromium.org>
Commit-Queue: Nick Sanders <nsanders@chromium.org>
Tested-by: Nick Sanders <nsanders@chromium.org>

[modify] https://crrev.com/c02b8e7253f3d1a711e136a1d47ae347e87ceba3/cbuildbot/config_dump.json
[modify] https://crrev.com/c02b8e7253f3d1a711e136a1d47ae347e87ceba3/cbuildbot/chromeos_config.py

Hi Philip, normally we don't touch factory branches until they are known to be needed. Does project Dumo need a new build of this branch or will it use a new factory branch? I think that Dumo had a very long list of changes so cherry-picking is likely to be difficult; that may affect your decision. Assign back to me on response.

Hi Jason,

We'll try to reuse the factory branch with some mosys hack (no unibuild).
See my second proposal in 'go/arm-sku-id', "Support factory flow for Dru and Dumo" section.
So it'll be great if pre-flight factory-scarlet-10211.B can be fixed.

Thank you, assigning to CIWI triage. Lann, this is likely to come up soon because of Dru/Domo projects.

I'm on leave.

Any update on this?