Due to a hilarious series of misadventures^W infrastructure and lab issues ( issue 859984 , issue 860166 , issue 860584, issue 860758 ), we have not had a Chrome uprev since July 2. This PFQ run: http://cros-goldeneye/chromeos/healthmonitoring/buildDetails?buildbucketId=8941795598155660624 had successful runs on all board builders but failed in UpdateChromeosLKGM due to issue 860584.
I've been unable to do this due to issue 860775 .
I think Chrome 69.0.3484.0 can be used instead now, as https://ci.chromium.org/p/chromeos/builders/luci.chromeos.general/Prod/b8941684121942150944 also would've passed if not for master-chromium-pfq failing in UpdateChromeosLKGM due to issue 860584. When that gets fixed, the command to run if you don't want to wait for an automated run (per the instructions at http://yaqs/eng/q/5592011371970560) would be: cros uprevchrome --pfq-build 2727704 -- bug chromium:860769
69.0.3488.0 (2740743) has succesful run on all bots. There are tree failures, but all of them are due to crbug.com/860508. https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8941258703774774272
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-partner-overlay/+/e50bac0950b272efd311481680ab29531bbdb835 commit e50bac0950b272efd311481680ab29531bbdb835 Author: Mitsuru Oshima <oshima@chromium.org> Date: Thu Jul 12 19:47:56 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/157e755860fb02d69e902a2f399ec515a18c6156 commit 157e755860fb02d69e902a2f399ec515a18c6156 Author: Mitsuru Oshima <oshima@chromium.org> Date: Thu Jul 12 19:47:33 2018 Manual Uprev Chrome: generated by cros_uprevchrome based on build_id 2740743, build_number 6771 Marking set of ebuilds as stable amd64-generic-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST arm-generic-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST daisy-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST veyron_jerry-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST amd64-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST Update profiles and manifests for Kernel. Update profiles and manifests for Chrome. Marking latest_release for chromium-source ebuild with version 69.0.3488.0 as stable. Marking latest_release for chromeos-chrome ebuild with version 69.0.3488.0 as stable. BUG= chromium:860769 TEST=None CQ-DEPEND=*Id36ed75ffbdc1b24e61d2b78027025d9b28ecdd9 Change-Id: Iad034b4ae8e2ec71232758077da77a8bfdfcbeb1 Reviewed-on: https://chromium-review.googlesource.com/1135641 Reviewed-by: Matthias Kaehlcke <mka@chromium.org> Reviewed-by: Steven Bennetts <stevenjb@chromium.org> Reviewed-by: Mitsuru Oshima <oshima@chromium.org> Tested-by: Mitsuru Oshima <oshima@chromium.org> Commit-Queue: Mitsuru Oshima <oshima@chromium.org> [rename] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/chromeos-base/chromium-source/chromium-source-69.0.3488.0_rc-r1.ebuild [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/sys-kernel/chromeos-kernel-3_18/Manifest [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/chromeos-base/chromeos-chrome/chromeos-chrome-9999.ebuild [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/chromeos/binhost/target/amd64-generic-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/sys-kernel/chromeos-kernel-3_8/chromeos-kernel-3_8-9999.ebuild [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/chromeos/binhost/target/daisy-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/sys-kernel/chromeos-kernel-4_4/Manifest [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/chromeos/binhost/target/arm-generic-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/sys-kernel/chromeos-kernel-3_14/chromeos-kernel-3_14-9999.ebuild [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/sys-kernel/chromeos-kernel-3_18/chromeos-kernel-3_18-9999.ebuild [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/sys-kernel/chromeos-kernel-3_14/Manifest [rename] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/chromeos-base/chromeos-chrome/chromeos-chrome-69.0.3488.0_rc-r1.ebuild [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/sys-kernel/chromeos-kernel-3_8/Manifest [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/sys-kernel/chromeos-kernel-4_4/chromeos-kernel-4_4-4.4.139-r1595.ebuild [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/sys-kernel/chromeos-kernel-3_8/chromeos-kernel-3_8-3.8.11-r732.ebuild [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/chromeos/binhost/target/veyron_jerry-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/sys-kernel/chromeos-kernel-3_18/chromeos-kernel-3_18-3.18-r2167.ebuild [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/sys-kernel/chromeos-kernel-4_4/chromeos-kernel-4_4-9999.ebuild [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/sys-kernel/chromeos-kernel-3_14/chromeos-kernel-3_14-3.14-r2047.ebuild [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/chromeos-base/chromeos-chrome/Manifest [modify] https://crrev.com/157e755860fb02d69e902a2f399ec515a18c6156/chromeos/binhost/host/amd64-LATEST_RELEASE_CHROME_BINHOST.conf
and here is the internal: https://chrome-internal-review.googlesource.com/c/chromeos/overlays/chromeos-partner-overlay/+/651363
Comment 1 by derat@chromium.org
, Jul 7