Reattaching correct /var/log/messages 

Deleted: messages.1 67.8 KB

messages.1 67.8 KB Download

Still seeing this on latest images, with Chrome version: 70.0.3530.0 and OS:10996.0.0.

However the test is passing if I build a Release version locally from TOT (70.0.3533.0) and deploy to the VM.

Will wait for Chrome to be uprev-ed by the Chrome PFQ and try again.

I'm still seeing this with SingleProcessMash with amd64-generic chrome 70.0.3538 platform 11042.0.0-rc2.

I hacked vm_sanity.py to only run this:

        mash_browser_args = ['--enable-features=SingleProcessMash',
                             '--gpu-no-complete-info-collection']

        logging.info('Testing Chrome with SingleProcessMash login.')
        with chrome.Chrome(extra_browser_args=mash_browser_args):
            logging.info('Chrome login with SingleProcessMash succeeded.')


I see this:

ERROR:root:Failed with BrowserGoneException while starting the browser backend.
INFO:root:*************** BROWSER STANDARD OUTPUT ***************
INFO:root:Cannot get standard output on CrOS
INFO:root:*********** END OF BROWSER STANDARD OUTPUT ************
INFO:root:********************* BROWSER LOG *********************
INFO:root:No log file
INFO:root:***************** END OF BROWSER LOG ******************
INFO:root:********************* SYMBOLIZED MINIDUMP *********************
INFO:root:***************** END OF SYMBOLIZED MINIDUMP ******************
...
INFO:root:Browser is closed.
INFO:root:Try printing formatted exception: <class 'telemetry.core.exceptions.BrowserGoneException'> [Errno 111] Connection refused
Found Minidump: False
Stack Trace:
********************************************************************************
	Cannot get stack trace on CrOS
********************************************************************************
Standard output:
********************************************************************************
	Cannot get standard output on CrOS
********************************************************************************
System log:
(Not implemented) <traceback object at 0x7bc4d9dad710>

Traceback (most recent call last):
  <module> at /usr/local/autotest/bin/vm_sanity.py:103
    sys.exit(main(sys.argv[1:]))
  main at /usr/local/autotest/bin/vm_sanity.py:99
    Sanity(count)
  Sanity at /usr/local/autotest/bin/vm_sanity.py:84
    with chrome.Chrome(extra_browser_args=mash_browser_args):
  __init__ at /usr/local/autotest/common_lib/cros/chrome.py:179
    self._browser = self._browser_to_create.Create()
  Create at /usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/cros_browser_finder.py:103
    browser_backend, self._platform_backend, startup_args)
  __init__ at /usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/cros_browser_with_oobe.py:14
    backend, platform_backend, startup_args)
  __init__ at /usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/browser/browser.py:49
    self._LogBrowserInfo()
  _LogBrowserInfo at /usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/browser/browser.py:107
    system_info = self.GetSystemInfo()
  GetSystemInfo at /usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/browser/browser.py:276
    return self._browser_backend.GetSystemInfo()
  traced_function at /usr/local/telemetry/src/third_party/catapult/common/py_trace_event/py_trace_event/trace_event_impl/decorators.py:52
    return func(*args, **kwargs)
  GetSystemInfo at /usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome/chrome_browser_backend.py:239
    raise exceptions.BrowserGoneException(self.browser, e)
BrowserGoneException: [Errno 111] Connection refused

Received signal 4 ILL_ILLOPN 5b971738de59
CFI: Most likely a control flow integrity violation; for more information see:
https://www.chromium.org/developers/testing/control-flow-integrity
#0 0x5b9715e0c2a3 <unknown>
#1 0x7956896852e0 <unknown>
#2 0x5b971738de59 <unknown>
#3 0x5b97178b95a9 <unknown>
#4 0x5b971858d868 <unknown>
#5 0x5b9713c17de1 <unknown>
#6 0x5b9715e79b10 [0912/145006:INFO:keygen_worker.cc(53)] Writing Owner key to /home/user/fa3944c822bd2843160153cc552cde19603c2e43/key.pub
<unknown>
#7 0x5b9715e7ff18 <unknown>
#8 0x5b9715e7f40d <unknown>
#9 0x5b9715e78634 <unknown>
#10 0x5b9715e79053 <unknown>
#11 0x5b9715e8f30d <unknown>
#12 0x5b9715e22568 <unknown>
#13 0x5b9715d7f187 <unknown>
#14 0x5b9715d7f897 <unknown>
#15 0x5b9715e1f015 <unknown>
#16 0x5b9715da3784 <unknown>
#17 0x5b97159a6360 <unknown>
#18 0x5b9713f7695e <unknown>
#19 0x5b9713f7a002 <unknown>
#20 0x5b9713f6ea4c <unknown>
#21 0x5b9715991bfb <unknown>
#22 0x5b9715999e7f <unknown>
#23 0x5b9713206435 <unknown>
#24 0x795688a67736 __libc_start_main

We need this to work if we want SingleProcessMash login to work. I'm going to try a tast test and see if things are different.

Like rcui, when I build my own chrome and deploy into the VM, everything works fine. No crash. :-(

This is true for both stripped and unstripped builds. You have to deploy into /tmp for unstripped.

deploy_chrome --build-dir=out_$SDK_BOARD/Release --to=localhost --port=9222 --nostrip --target-dir=/tmp/mychrome --mount-dir=/opt/google/chrome

I rewrote this test using Tast and everything works fine. Change is in the CQ: https://chromium-review.googlesource.com/c/chromiumos/platform/tast-tests/+/1222157

I'm going to go with the Tast version and not worry about this.