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

commit 69d40ae178a50abb5d3f3093b5c0745438c23709
Author: Stephen Barber <smbarber@chromium.org>
Date: Thu Mar 22 10:01:29 2018

tael: remove USE for kernel-4_4

The project-termina overlay already sets the kernel-4_14 USE flag. Remove
the kernel-4_4 flag from tael, since that will confuse portage when trying
to actually pick the right kernel.

BUG= chromium:824615 
TEST=./build_packages --board=tael --nowithautotest

Change-Id: I65343e145363de387edf1d5dc561c26b6e782d2b
Reviewed-on: https://chromium-review.googlesource.com/974785
Commit-Ready: Stephen Barber <smbarber@chromium.org>
Tested-by: Stephen Barber <smbarber@chromium.org>
Reviewed-by: Dylan Reid <dgreid@chromium.org>

[modify] https://crrev.com/69d40ae178a50abb5d3f3093b5c0745438c23709/overlay-tael/profiles/base/make.defaults

Adding infra deputies - I think this may require new GCE instances for the external waterfall.

Don, do you know what actions are needed here?

Have the build configs been created yet, and added to the proper waterfalls?

If so, allocating builders will happen during the pin bump / waterfall restart process.

Ah okay, the build configs are in https://chromium-review.googlesource.com/c/chromiumos/chromite/+/982563

Thanks, I'll specify that new builders are needed when I ask for the waterfall restart.

I'll remove infra people then to reduce noise.

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

commit 7017df438ed3652f4095a51536b11f715bd04fcb
Author: chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Fri Mar 30 06:23:43 2018

Roll src/third_party/chromite/ 33146a204..36a9c890b (5 commits)

https://chromium.googlesource.com/chromiumos/chromite.git/+log/33146a20418a..36a9c890b979

$ git log 33146a204..36a9c890b --date=short --no-merges --format='%ad %ae %s'
2018-03-29 yunlian Add USE=thinlto for AMD64 release buidlers only.
2018-03-29 vapier gs: update to 4.30
2018-03-29 yunlian chromeos-config: remove USE=thinlto from terra and caroline-release
2018-03-27 smbarber chromeos_config: add tael to external waterfall
2018-03-28 dgarrett precq: Add eve-no-vmtest-pre-cq.

Created with:
  roll-dep src/third_party/chromite
BUG= chromium:827217 ,chromium:None,chromium:707803,chromium:824615,chromium:820252


The AutoRoll server is located here: https://chromite-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=chrome-os-gardeners@chromium.org

Change-Id: I83683cdbd852c5097195bb0689107322912eeb7f
Reviewed-on: https://chromium-review.googlesource.com/987452
Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#547117}
[modify] https://crrev.com/7017df438ed3652f4095a51536b11f715bd04fcb/DEPS

This builder is active now, but is quite red.

 crbug.com/829598 
 crbug.com/829601 

I think this builder is green now -- not sure about 829598 -- I don't see it locally and the builder was green when the fix for 829601 was being tested

nevermind -- the paladin builder is green but the full builder is still red on building openssl.  Not clear how the paladin builder is green -- might be getting a binary package built with GCC or something.

full builder is green now