Manually update Chrome on Chrome OS to 58.0.3015.0 |
|||||||
Issue description
The Chrome PFQ failed in two ways in build id 1323125
Falco failed with an infra failure in provisioning
provision: FAIL: Unhandled DevServerException: CrOS auto-update failed for host chromeos2-row3-rack3-host9: RootfsUpdateError: Failed to perform rootfs update: DevServerStartupError('Devserver portfile does not exist!',)
Tricky failed in the pfq with:
02/13 21:47:58.778 WARNI| platform_MemCheck:0079| SwapTotal is 0
and the kernel log has
2017-02-13T21:46:57.422109-08:00 NOTICE swap[2012]: swapon /dev/zram0 failed, try 11
which sounds like swap failed to enable, it is not clear why, and it seems unlikely that this was related to the new Chrome, the boot prior in messages successfully swaponed zram.
As neither of these appear to be related to the new Chrome, and we need a new Chrome for the upcoming 58 dev, we should manually uprev.
,
Feb 14 2017
Looks like it can't connect to the database. We recently changed the CIDB password, can you update your credentials and try again?
,
Feb 17 2017
The Chrome PFQ failed in two ways in build id 1329930 cyan failed with HWTest for timeout, but it succeeded in an earlier build 788 https://chromegw.corp.google.com/i/chromeos/builders/cyan-chrome-pfq/builds/790 daisy_skate failed for DUT rebooting during the test issue. https://chromegw.corp.google.com/i/chromeos/builders/daisy_skate-chrome-pfq/builds/3506 But it succeeded in a later run 3507, and there is not real difference in cl between chrome version 3015.3 and 3015.0. This means it could have a good run with 3015.0 As neither of these appear to be related to the new Chrome, and we need a new Chrome for the upcoming 58 dev, we should manually uprev.
,
Feb 17 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-partner-overlay/+/82692b66b3afe7c32e85e4b8d37f6e5bdd0021c3 commit 82692b66b3afe7c32e85e4b8d37f6e5bdd0021c3 Author: Jenny Zhang <jennyz@chromium.org> Date: Fri Feb 17 23:39:56 2017
,
Feb 17 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/5e61d02d0c270ae5c04084d40183cc318b41de8e commit 5e61d02d0c270ae5c04084d40183cc318b41de8e Author: Jenny Zhang <jennyz@chromium.org> Date: Fri Feb 17 23:41:20 2017 Manual Uprev Chrome: generated by cros_uprevchrome based on build_id 1329930, build_number 3997 Marking set of ebuilds as stable amd64-generic-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST x86-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 "Set {arch: afdo_file} pairs {'arm': 'chromeos-chrome-amd64-58.0.3015.0_rc-r1.afdo', 'x86': 'chromeos-chrome-amd64-58.0.3015.0_rc-r1.afdo', 'amd64': 'chromeos-chrome-amd64-58.0.3015.0_rc-r1.afdo'} and updated Manifest" "Set {arch: afdo_file} pairs {'arm': 'chromeos-chrome-amd64-58.0.3015.0_rc-r1.afdo', 'x86': 'chromeos-chrome-amd64-58.0.3015.0_rc-r1.afdo', 'amd64': 'chromeos-chrome-amd64-58.0.3015.0_rc-r1.afdo'} and updated Manifest" Marking latest_release for chromium-source ebuild with version 58.0.3015.0 as stable. Marking latest_release for chromeos-chrome ebuild with version 58.0.3015.0 as stable. BUG= chromium:691924 TEST=None CQ-DEPEND=*I309df27ad23e82b14d2552657a2560f8c951fab5 Change-Id: Ie2c89aa6df0da48eecadf0454294c06185ed1972 Reviewed-on: https://chromium-review.googlesource.com/444925 Reviewed-by: Aviv Keshet <akeshet@chromium.org> Reviewed-by: Shuqian Zhao <shuqianz@chromium.org> Reviewed-by: Jenny Zhang <jennyz@chromium.org> Tested-by: Jenny Zhang <jennyz@chromium.org> [rename] https://crrev.com/5e61d02d0c270ae5c04084d40183cc318b41de8e/chromeos-base/chromium-source/chromium-source-58.0.3015.0_rc-r1.ebuild [modify] https://crrev.com/5e61d02d0c270ae5c04084d40183cc318b41de8e/chromeos-base/chromeos-chrome/chromeos-chrome-9999.ebuild [modify] https://crrev.com/5e61d02d0c270ae5c04084d40183cc318b41de8e/chromeos/binhost/target/amd64-generic-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/5e61d02d0c270ae5c04084d40183cc318b41de8e/chromeos/binhost/target/daisy-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/5e61d02d0c270ae5c04084d40183cc318b41de8e/chromeos/binhost/target/arm-generic-LATEST_RELEASE_CHROME_BINHOST.conf [rename] https://crrev.com/5e61d02d0c270ae5c04084d40183cc318b41de8e/chromeos-base/chromeos-chrome/chromeos-chrome-58.0.3015.0_rc-r1.ebuild [modify] https://crrev.com/5e61d02d0c270ae5c04084d40183cc318b41de8e/chromeos/binhost/target/x86-generic-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/5e61d02d0c270ae5c04084d40183cc318b41de8e/chromeos/binhost/target/veyron_jerry-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/5e61d02d0c270ae5c04084d40183cc318b41de8e/chromeos-base/chromeos-chrome/Manifest [modify] https://crrev.com/5e61d02d0c270ae5c04084d40183cc318b41de8e/chromeos/binhost/host/amd64-LATEST_RELEASE_CHROME_BINHOST.conf
,
Feb 21 2017
The manual uprev works. See GoldenEye page, the chrome has been uprev to 58.0.3015.0.
,
Feb 24 2017
Reopening. There is believe at the moment that this uprev broke a lot of video tests. Is there evidence that this passed the relevant tests?
,
Feb 24 2017
+derat who is thinking a lot about cq vs pfq test coverage
,
Jul 27 2017
,
Aug 3 2017
Obsolete |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by bhthompson@google.com
, Feb 14 2017