New issue
Advanced search Search tips

Issue 814445 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

tatl: promote from experimental paladin

Project Member Reported by smbar...@chromium.org, Feb 21 2018

Issue description

tatl has been green for a long time, and isn't running any tests right now anyway. Promote this from experimental so the CQ will keep out build breakages.
 
Labels: Proj-Containers
Cc: chirantan@chromium.org tbuck...@chromium.org dgreid@chromium.org
Labels: -Pri-3 Pri-1
Two CLs that would have been caught by an important paladin have broken tatl in the past week and are blocking VM uprevs.

https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/942502
https://chromium-review.googlesource.com/c/chromiumos/overlays/portage-stable/+/969622

Increasing priority.
Project Member

Comment 3 by bugdroid1@chromium.org, Mar 22 2018

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

commit 051b1952ca4b29bde5f5b1f07ce0e1fff20d9fce
Author: Stephen Barber <smbarber@chromium.org>
Date: Thu Mar 22 06:23:42 2018

chromeos_config: promote tatl from experimental

tatl has been reliably green, so promote it from experimental.

BUG= chromium:814445 
TEST=chromeos_config unittests

Change-Id: I94f9f8179554759fdf2773574e2be97632c21717
Reviewed-on: https://chromium-review.googlesource.com/929447
Commit-Ready: Stephen Barber <smbarber@chromium.org>
Tested-by: Stephen Barber <smbarber@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

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

Status: Fixed (was: Started)
Project Member

Comment 5 by bugdroid1@chromium.org, Mar 22 2018

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

commit c55a0e3aa13c32d07b72ae7066c405808e8ae595
Author: chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Date: Thu Mar 22 11:39:44 2018

Roll src/third_party/chromite/ a1ec7e112..051b1952c (2 commits)

https://chromium.googlesource.com/chromiumos/chromite.git/+log/a1ec7e112c5e..051b1952ca4b

$ git log a1ec7e112..051b1952c --date=short --no-merges --format='%ad %ae %s'
2018-02-21 smbarber chromeos_config: promote tatl from experimental
2018-03-21 dgarrett chromeos_config: Mark master-release as important.

Created with:
  roll-dep src/third_party/chromite
BUG= chromium:814445 , chromium:824582 


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: I7e9f8ce027937ff3b065c25f4c97e1ef77169f07
Reviewed-on: https://chromium-review.googlesource.com/974905
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@{#545041}
[modify] https://crrev.com/c55a0e3aa13c32d07b72ae7066c405808e8ae595/DEPS

Sign in to add a comment