Uprev chrome to 60.0.3077.0 for Chrome OS |
|||||
Issue descriptionmaster-chromium-pfq #4250 only had one failure. https://uberchromegw.corp.google.com/i/chromeos/builders/master-chromium-pfq/builds/4250 daisy_skate-chrome-pfq: The HWTest [bvt-cq] stage failed: ** HWTest failed (code 1) ** Failure: network_DefaultProfileCreation FAIL: Autotest client terminated unexpectedly: DUT rebooted during the test run. The failure details appear to match symptoms in issue 697274: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/113598716-chromeos-test/ (See logs in crashinfo.chromeos4-row9-rack6-host1) Conclusion: The PFQ run had only one known issue and we should move forward with this Chrome version.
,
Apr 21 2017
build_id: 1466024 Command: $ cros uprevchrome --pfq-build 1466024 --cred-dir ~/Work/prod_cidb_readonly/ -- bug chromium:714170
,
Apr 21 2017
,
Apr 21 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/overlays/chromeos-partner-overlay/+/86ef0679ae1ab7a83bd534bbec94f5982f79bda6 commit 86ef0679ae1ab7a83bd534bbec94f5982f79bda6 Author: xdai <xdai@chromium.org> Date: Fri Apr 21 16:51:08 2017
,
Apr 21 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/ee2e2d547fd302242f35c133451dd4a318e524ec commit ee2e2d547fd302242f35c133451dd4a318e524ec Author: xdai <xdai@chromium.org> Date: Fri Apr 21 16:51:18 2017 Manual Uprev Chrome: generated by cros_uprevchrome based on build_id 1466024, build_number 4250 Marking set of ebuilds as stable x86-generic-LATEST_RELEASE_CHROME_BINHOST.conf: updating LATEST_RELEASE_CHROME_BINHOST 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 "Set {arch: afdo_file} pairs {'arm': 'chromeos-chrome-amd64-60.0.3077.0_rc-r1.afdo', 'x86': 'chromeos-chrome-amd64-60.0.3077.0_rc-r1.afdo', 'amd64': 'chromeos-chrome-amd64-60.0.3077.0_rc-r1.afdo'} and updated Manifest" "Set {arch: afdo_file} pairs {'arm': 'chromeos-chrome-amd64-60.0.3077.0_rc-r1.afdo', 'x86': 'chromeos-chrome-amd64-60.0.3077.0_rc-r1.afdo', 'amd64': 'chromeos-chrome-amd64-60.0.3077.0_rc-r1.afdo'} and updated Manifest" Marking latest_release for chromium-source ebuild with version 60.0.3077.0 as stable. Marking latest_release for chromeos-chrome ebuild with version 60.0.3077.0 as stable. BUG= chromium:714170 TEST=None CQ-DEPEND=*I2dab8fca8bdb4c692ccb635ccd81d2c564d93ac0 Change-Id: Icd0526204e4e0bdd897a0988617ed067832d91d5 Reviewed-on: https://chromium-review.googlesource.com/483806 Reviewed-by: Steven Bennetts <stevenjb@chromium.org> Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org> Tested-by: Xiaoqian Dai <xdai@chromium.org> [modify] https://crrev.com/ee2e2d547fd302242f35c133451dd4a318e524ec/chromeos-base/chromeos-chrome/chromeos-chrome-9999.ebuild [modify] https://crrev.com/ee2e2d547fd302242f35c133451dd4a318e524ec/chromeos/binhost/target/amd64-generic-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/ee2e2d547fd302242f35c133451dd4a318e524ec/chromeos/binhost/target/daisy-LATEST_RELEASE_CHROME_BINHOST.conf [rename] https://crrev.com/ee2e2d547fd302242f35c133451dd4a318e524ec/chromeos-base/chromium-source/chromium-source-60.0.3077.0_rc-r1.ebuild [modify] https://crrev.com/ee2e2d547fd302242f35c133451dd4a318e524ec/chromeos/binhost/target/arm-generic-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/ee2e2d547fd302242f35c133451dd4a318e524ec/chromeos/binhost/target/x86-generic-LATEST_RELEASE_CHROME_BINHOST.conf [modify] https://crrev.com/ee2e2d547fd302242f35c133451dd4a318e524ec/chromeos/binhost/target/veyron_jerry-LATEST_RELEASE_CHROME_BINHOST.conf [rename] https://crrev.com/ee2e2d547fd302242f35c133451dd4a318e524ec/chromeos-base/chromeos-chrome/chromeos-chrome-60.0.3077.0_rc-r1.ebuild [modify] https://crrev.com/ee2e2d547fd302242f35c133451dd4a318e524ec/chromeos-base/chromeos-chrome/Manifest [modify] https://crrev.com/ee2e2d547fd302242f35c133451dd4a318e524ec/chromeos/binhost/host/amd64-LATEST_RELEASE_CHROME_BINHOST.conf
,
Apr 21 2017
For context: the CQ and PFQ were caught in a vice between crbug.com/713968 in a previously recent chrome (taking down the lab) and crbug.com/713531 in the pinned-back-to chrome.
,
Apr 22 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/885017e92f0936b001f04167374c32821c953de9 commit 885017e92f0936b001f04167374c32821c953de9 Author: Aviv Keshet <akeshet@chromium.org> Date: Sat Apr 22 04:57:53 2017 Revert "temporarily move security_SandboxStatus out of bvt-inline" Chrome was manually uprevved, so we should be passed this issue. This reverts commit 551c10669608ff2aaf270273026043d143fa1c56. BUG= chromium:713531 , 714170 TEST=None Change-Id: Icd405271e76a134cf2568d2bc546573e4109dfcd Reviewed-on: https://chromium-review.googlesource.com/483968 Commit-Ready: Aviv Keshet <akeshet@chromium.org> Tested-by: Aviv Keshet <akeshet@chromium.org> Reviewed-by: Steven Bennetts <stevenjb@chromium.org> Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org> [modify] https://crrev.com/885017e92f0936b001f04167374c32821c953de9/client/site_tests/security_SandboxStatus/control
,
May 1 2017
,
Aug 1 2017
,
Aug 3 2017
Closing. Please reopen it if its not fixed. Thanks! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by steve...@chromium.org
, Apr 21 2017