Issue metadata
Sign in to add a comment
|
GPU bots failed with "Your 'Oauth 2.0 User Account' credentials are invalid" error |
||||||||||||||||||||||||
Issue descriptionFor example, this one: Pixel_tests in this one: https://ci.chromium.org/buildbot/tryserver.chromium.win/win7_chromium_rel_ng/67939 Downloading gs://chromium-gpu-archive/reference-images/Pixel_2DCanvasWebGL_v5_win_10de_1cb3_msaa.png to c:\b\s\w\ityyiawm\tmpp3dznr.png Traceback (most recent call last): _RunGpuTest at content\test\gpu\gpu_tests\gpu_integration_test.py:132 self.RunActualGpuTest(url, *args) RunActualGpuTest at content\test\gpu\gpu_tests\pixel_integration_test.py:157 ref_png = self._DownloadFromCloudStorage(image_name, page, tab) _DownloadFromCloudStorage at content\test\gpu\gpu_tests\cloud_storage_integration_test_base.py:321 temp_file) Get at third_party\catapult\common\py_utils\py_utils\cloud_storage.py:237 _GetLocked(bucket, remote_path, local_path) _GetLocked at third_party\catapult\common\py_utils\py_utils\cloud_storage.py:349 _RunCommand(['cp', url, partial_download_path.name]) _RunCommand at third_party\catapult\common\py_utils\py_utils\cloud_storage.py:154 raise GetErrorObjectForCloudStorageStderr(stderr) CloudStorageError: Your "Oauth 2.0 User Account" credentials are invalid. For more help, see "gsutil help creds", or re-run the gsutil config command (see "gsutil help config"). Failure: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661). Locals: args : ['c:\\infra-system\\bin\\python.exe', 'c:\\b\\s\\w\\ir\\third_party\\catapult\\third_party\\gsutil\\gsutil', 'cp', 'gs://chromium-gpu-archive/reference-images/Pixel_2DCanvasWebGL_v5_win_10de_1cb3_msaa.png', 'c:\\b\\s\\w\\ityyiawm\\tmpmewcp4'] gsutil : <subprocess.Popen object at 0x0000000004D95C88> gsutil_env : None stderr : 'Your "Oauth 2.0 User Account" credentials are invalid. For more help, see "gsutil help creds", or re-run the gsutil config command (see "gsutil help config").\r\nFailure: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661).\r\n' stdout : '' Found crashpad_database_util No minidump found via crashpad_database_util No minidump paths to symbolize Found crashpad_database_util No minidump found via crashpad_database_util Restarting browser due to unexpected test failure Closing browser (pid=4120) ... [4120:2644:1218/152359.295:INFO:chrome_cryptauth_service.cc(233)] Profile is not authenticated yet; waiting before starting CryptAuth managers. [4120:2644:1218/152359.556:WARNING:url_request_context_getter.cc(43)] URLRequestContextGetter leaking due to no owning thread. Successfully shut down browser cooperatively Browser is closed. Requested remote debugging port: 0 Starting Chrome ['c:\\b\\s\\w\\ir\\out\\Release\\chrome.exe', '--force-color-profile=srgb', '--test-type=gpu', '--enable-gpu-benchmarking', '--js-flags=--expose-gc', '--enable-logging=stderr', '--ensure-forced-color-profile', '--enable-net-benchmarking', '--metrics-recording-only', '--no-default-browser-check', '--no-first-run', '--enable-gpu-benchmarking', '--autoplay-policy=no-user-gesture-required', '--disable-background-networking', '--proxy-server=socks://localhost:51761', '--ignore-certificate-errors-spki-list=PhrPvGIaAMmd29hj8BCZOq096yj7uMpRNHpn5PDxI6I=', '--disable-component-extensions-with-background-pages', '--disable-default-apps', '--disable-search-geolocation-disclosure', '--remote-debugging-port=0', '--enable-crash-reporter-for-testing', '--disable-component-update', '--window-size=1280,1024', '--user-data-dir=c:\\b\\s\\w\\ityyiawm\\tmpdzlqnp', 'about:blank'] [4300:5032:1218/152359.637:ERROR:memory_mapped_file.cc(53)] Couldn't open c:\b\s\w\ir\out\Release\chrome_200_percent.pak [4300:5032:1218/152359.637:ERROR:data_pack.cc(251)] Failed to mmap datapack
,
Dec 19 2017
,
Dec 19 2017
Thanks. :)
,
Feb 23 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/aed54bbe528df1a8627d46c74ef97d55686640e9 commit aed54bbe528df1a8627d46c74ef97d55686640e9 Author: Evan Green <evgreen@chromium.org> Date: Fri Feb 23 11:36:14 2018 CHROMIUM: config: Add missing qualcomm-config features This change adds the serial configs needed to boot the SDM845 MTP to a RAM disk. It also flips on the I2C GENI, since we'll need that too. To generate the config, I did the following: cat >>chromeos/config/arm64/chromiumos-qualcomm.flavour.config <<_EOF CONFIG_QCOM_GENI_SE=y CONFIG_SDM_GCC_845=y CONFIG_SERIAL_QCOM_GENI=y CONFIG_I2C_QCOM_GENI=y _EOF cat >>chromeos/config/arm64/chromiumos-arm64.flavour.config <<_EOF CONFIG_QCOM_GENI_SE=y CONFIG_SDM_GCC_845=y CONFIG_SERIAL_QCOM_GENI=y CONFIG_I2C_QCOM_GENI=y _EOF BUG= chromium:795964 TEST=Build kernel for Cheza Change-Id: Ifa01db23dd409329a8b5b10135e00b05ce39b301 Signed-off-by: Evan Green <evgreen@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/890162 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> [modify] https://crrev.com/aed54bbe528df1a8627d46c74ef97d55686640e9/chromeos/config/arm64/chromiumos-arm64.flavour.config [modify] https://crrev.com/aed54bbe528df1a8627d46c74ef97d55686640e9/chromeos/config/armel/common.config [modify] https://crrev.com/aed54bbe528df1a8627d46c74ef97d55686640e9/chromeos/config/arm64/chromiumos-mediatek.flavour.config [modify] https://crrev.com/aed54bbe528df1a8627d46c74ef97d55686640e9/chromeos/config/base.config [modify] https://crrev.com/aed54bbe528df1a8627d46c74ef97d55686640e9/chromeos/config/i386/common.config [modify] https://crrev.com/aed54bbe528df1a8627d46c74ef97d55686640e9/chromeos/config/arm64/chromiumos-rockchip64.flavour.config [modify] https://crrev.com/aed54bbe528df1a8627d46c74ef97d55686640e9/chromeos/config/x86_64/common.config [modify] https://crrev.com/aed54bbe528df1a8627d46c74ef97d55686640e9/chromeos/config/arm64/chromiumos-qualcomm.flavour.config |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by kbr@chromium.org
, Dec 19 2017Components: Tests>Telemetry