Shrawan,
can you try M53 cheets enabled build on samus and test reboot with HDMI external connection to monitor, and share results?

I recovered the Samus with Samus-cheets build (8448.0.0_samus-cheets) and tried both the test (display_HotPlugAtBoot.extended, display_HotPlugAtBoot.mirrored) manually. 

Both of the test passed consistently.

The failure is
06/13 17:42:28.573 WARNI|              test:0606| Autotest caught exception when running test:
Traceback (most recent call last):
  File "/usr/local/autotest/client/common_lib/test.py", line 600, in _exec
    _call_test_function(self.execute, *p_args, **p_dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 810, in _call_test_function
    raise error.UnhandledTestFail(e)
UnhandledTestFail: Unhandled Exception: RPC error: display.close_tab
Traceback (most recent call last):
  File "./multimedia_xmlrpc_server.py", line 68, in _dispatch
    return func(*params)
  File "/usr/local/autotest/cros/multimedia/display_facade_native.py", line 669, in close_tab
    self._resource.close_tab(tab_descriptor)
  File "/usr/local/autotest/common_lib/cros/retry.py", line 171, in func_retry
    remaining_time)
  File "/usr/local/autotest/common_lib/cros/retry.py", line 95, in timeout
    default_result = func(*args, **kwargs)
  File "/usr/local/autotest/cros/multimedia/facade_resource.py", line 187, in close_tab
    raise RuntimeError('There is no tab for %s' % tab_descriptor)
RuntimeError: There is no tab for 0x7feafbbf5490

Traceback (most recent call last):
  File "/usr/local/autotest/client/common_lib/test.py", line 804, in _call_test_function
    return func(*args, **dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 461, in execute
    dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 347, in _call_run_once_with_retry
    postprocess_profiled_run, args, dargs)
  File "/usr/local/autotest/client/common_lib/test.py", line 376, in _call_run_once
    self.run_once(*args, **dargs)
  File "/usr/local/autotest/server/site_tests/display_HotPlugAtBoot/display_HotPlugAtBoot.py", line 99, in run_once
    resolution, test_mirrored, errors):
  File "/usr/local/autotest/client/cros/chameleon/chameleon_screen_test.py", line 136, in test_screen_with_image
    self.unload_test_image()
  File "/usr/local/autotest/client/cros/chameleon/chameleon_screen_test.py", line 97, in unload_test_image
    self._display_facade.close_tab(self._calibration_image_tab_descriptor)
  File "/usr/local/autotest/server/cros/multimedia/display_facade_adapter.py", line 126, in close_tab
    self._display_proxy.close_tab(tab_descriptor)
  File "/usr/local/autotest/server/cros/multimedia/remote_facade_factory.py", line 42, in __call__
    return self.__call_method(self.__name, *args, **dargs)
  File "/usr/local/autotest/server/cros/multimedia/remote_facade_factory.py", line 92, in __call_proxy
    raise Exception('RPC error: %s\n%s' % (name, value))
Exception: RPC error: display.close_tab
Traceback (most recent call last):
  File "./multimedia_xmlrpc_server.py", line 68, in _dispatch
    return func(*params)
  File "/usr/local/autotest/cros/multimedia/display_facade_native.py", line 669, in close_tab
    self._resource.close_tab(tab_descriptor)
  File "/usr/local/autotest/common_lib/cros/retry.py", line 171, in func_retry
    remaining_time)
  File "/usr/local/autotest/common_lib/cros/retry.py", line 95, in timeout
    default_result = func(*args, **kwargs)
  File "/usr/local/autotest/cros/multimedia/facade_resource.py", line 187, in close_tab
    raise RuntimeError('There is no tab for %s' % tab_descriptor)
RuntimeError: There is no tab for 0x7feafbbf5490



Now, actually samus has not yet merged with the -cheets build. So this is not yet ARC++ enabled build.
Still, I'll retest with and without my change and see result.

Tom, any idea why this missing tab failure is present?

I re-ran the test with and without the arc_mode argument passed to Chrome instance, and it did not change - both cases failed same way. 
Therefore no fault in the way Chrome starts with arc_mode enabled or not.

Tom, can you pls take a look?

Assigned to mojahsu@ to investigate the missing tab error.

By the log, the exception happened after the retry process.
But looks like we should have the tab descriptor. I will add more logs to figure out what happened.

From the logs in https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/66689418-chromeos-test/android1758-audiobox5-host2/ I can see sysinfo archive includes a chrome crash.
It might be the reason to loose the chrome tab.

The pass log is looks like this
06/15 10:51:14.970 INFO | mirror_comparison:0059| Sofware-based mirroring, skip the screen 
06/15 10:51:15.639 INFO |remote_facade_fact:0093| RPC 'display.close_tab'(('0x7f9cb3962b10',), {}) returns True.
06/15 10:51:15.640 INFO |display_HotPlugAtB:0066| TESTING THE CASE: plug > reboot > unplug

The execution time for close_tab is very short, it's about 0.7 seconds from previous log to the close_tab log.

But for the exception log,

06/13 17:33:16.044 INFO |chameleon_screen_t:0134| Retry screen comparison again...
06/13 17:34:17.330 ERROR|remote_facade_fact:0109| Failed RPC 'display.close_tab'(('0x7fb52f325dd0',), {}) with status [<type 'exceptions.Exception'>].
It took 1 minute to get RPC reply. So the chrome must be crash.
Can we assign this issue to related owner? Looks like it is not chameleon issue.

Maybe we can sync the time in multimedia_xmlrpc_server.log

17:32:31 INFO | Dispatching method <bound method DisplayFacadeNative.load_calibration_image of <autotest_lib.client.cros.multimedia.display_facade_native.DisplayFacadeNative object at 0x7fb52f325d50>> with args ([1280, 850],)
...
...
17:33:15 INFO | Dispatching method <bound method DisplayFacadeNative.close_tab of <autotest_lib.client.cros.multimedia.display_facade_native.DisplayFacadeNative object at 0x7fb52f325d50>> with args ('0x7fb52f325dd0',)
17:33:15 WARNI| <class 'telemetry.internal.backends.chrome_inspector.devtools_http.DevToolsClientConnectionError'>('')
17:33:15 WARNI| Retrying in 0.904758 seconds...

We have backends error when we want to close the tab.
and then

Found Minidump: False
Stack Trace:
********************************************************************************
        Cannot get stack trace on CrOS

Is it for CrOs crash?
After that we still retry to close_tab, so we will get no tab exception.

Kalin, what did the screen look like when during the test failing to close the tab? Chrome crashed?

Is it reproducible manually?

I tested non-cheets board and on build 8456.0.0 (still not tested in lab on samus), and rebooting went smooth and after user login chrome browser behaved good.

I'd suspect this is happening only with lab setup. 

Will observe lab setup board execution.

I tested 8469.0.0 non-cheets and cheets images on samus chromebook locally. It passed the case for DP and HDMI(by HOHO).
Can we reimage the chromebook in LAB back to the 8427.0.0(the last passed image) and do the test again? 

Moja, you can schedule a job to run it on a specific build, like 8427.0.0, like:
$ site_utils/run_suite.py --board samus --build samus-release/R53-8427.0.0 --pool chameleon --suite_name chameleon_hdmi_perbuild

I created a job on:
http://cautotest.corp.google.com/afe/#tab_id=view_job&object_id=67314145

Let's wait the result to clarify.

I locked the DUT, re-imaged it with R53-8427.0.0 (cros flash with --clobber-stateful) and reran both tests. They failed same way - so, something bad might be on the audio box imege/setup side.

I'll be returning R53-8466.0.0, so DUT does not get in repair state. Till after when unlocking the DUT your job will not be running.

Now I am experimenting with chromeos1-row1-rack3-host6.

Testing on chromeos1-row1-rack3-host6 PASSED both tests.

We need to re-check the setup at the audio box at android1758-audiobox5-host2.

Shrawan, please do the following:
1) swap DUTs between android1758-audiobox5-host2 and chromeos1-row1-rack3-host6. Lock them first on cautotest.
2) At android1758-audiobox5-host2 
- shut down chameleon, and servo
- unplig all cables
- plug them back
- be sure all setup is good
- start chameleon and servo (and DUT)

3) Run test display_ServerChameleonConnection to confirm connection is good
test_that -b squawks chromeos1-row1-rack3-host6 display_ServerChameleonConnection

4) Run the two tests that fail for this bug:
test_that -b squawks chromeos1-row1-rack3-host6 display_HotPlugAtBoot.extended display_HotPlugAtBoot.mirrored

5) Update this bug

Replaced the DUT at android1758-audiobox5-host2. Re-cabled all connections and powered up DUT, servo and chameleon as directed in #16 comment 2nd step.


DUT is in good state and passing display_ServerChameleonConnection, display_HotPlugAtBoot.extended display_HotPlugAtBoot.mirrored test ran from chroot.

Great, thanks Shrawan,
Please re-image the DUT you took from this audio box, and deploy at chromeos1-row1-rack3-host6. Lets see how is it going to do there.

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

chromeos1-row1-rack3-host6 still failed in display_HotPlugAtBoot with RPC error: display.close_tab:
https://wmatrix.googleplex.com/testrun/unfiltered?test_ids=320559018

This owner is not able to receive e-mails, please re-triage.

Verified.
https://wmatrix.googleplex.com/platform/unfiltered?hide_missing=True&tests=display_HotPlugAtBoot.mirrored&releases=tot&platforms=samus