[chameleon hdmi] display_Resolution.extended fails consistently on resolution [1440, 900] with RuntimeError: There is no tab for 0x75275a33eed0 (RPC: display.close_tab) since R69-10788.0.0 |
|||||
Issue descriptionDashboard screenshot: https://screenshot.googleplex.com/tPW72zjwhSj Same failure reason started on some other extended mode tests(display_HotPlugAtSuspend, display_HotPlugAtBoot, display_LidCloseOpen) for four boards - chell, cyan,eve,kevin,lars https://screenshot.googleplex.com/oPssi52Hkg1 It looks like chrome tab is closed after resolution is changed to 1440x900. It can be caused by a browser crash. There are selinux_violation crash files(auron_paine), but they are present for other even PASSED tests too. Further investigation is needed. AI: Manual checks for extended mode external display to confirm any issues.
,
Jun 18 2018
Chrome diff - https://chromium.googlesource.com/chromium/src/+log/69.0.3457.0..69.0.3462.0?n=10000 ChromeOs diff - https://crosland.corp.google.com/log/10787.0.0..10788.0.0 +malaykeshav, would https://chromium-review.googlesource.com/c/chromium/src/+/1101936 be related here?
,
Jun 18 2018
Are these auto tests? How do I repro them locally?
,
Jun 18 2018
Yes, autotest. Testing team will re-test manually the scenario Set first 1280x800, and observe the extended display then set 1440x900, and observe the extended display(issue should show up here)
,
Jun 18 2018
,
Jun 18 2018
Not able to reproduce this issue on Eve.
Tested Build: 10795.0.0
Dut: EVE
Steps followed:
1. Sign in to the device.
2. Connected external display using type C to HDMI converter.
-- Extended display is working fine.
3. Change to all listed external display resolutions.
-- All resolutions are working fine.
-- Did not notice any crash or any reconnecting message.
4. Change the external display resolution to 1280x800
5. Change the external display resolution to 1440x900.
6. Change the external display resolution to 1280x800
7. Reboot the device and sign in to the device.
8. Change the external display resolution to 1280x800
--Extended display is working fine. Did not notice any issue.
,
Jun 18 2018
,
Jun 18 2018
The test is using the telemetry display autotest extension to set the resolution at https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/client/cros/multimedia/display_test_extension/ Would something in the log at https://storage.cloud.google.com/chromeos-autotest-results/209520346-chromeos-test/chromeos2-row10-rack7-host11/debug/autoserv.DEBUG indicate extension is problematic test resolution [1440, 900]?
,
Jun 18 2018
The expectations from the system display API did change in M68 for internal displays. However, I am not sure if that is causing the failure. We introduced a new feature that results in there being one 1 display resolution available for the internal display. But the system display API protocol itself has not changed, so it shouldn't be causing a crash. Looking at the debug closely, it looks like the test fails to load the calibration image for the the 1440x900 external display resolution?
,
Jul 16
Same as issue 850986, this was resolved somehow for most of the test that failed with 'There is no tab for 0x75275a33eed0 (RPC: display.close_tab)'. So this magically starts with R69-10757.0.0 and then disappears(phew)magically with - R69-10820.0.0 for cyan(3.18) and lars(3.18) - R69-10872.0.0 for chell(3.18), coral(4.4), eve(4.4),and suposedly pyro(4.4) - R69-10879.0.0 - display_Resolution.extended fixed for all boards Dashboard view screenshot: https://screenshot.googleplex.com/YAPpUArsm6m Marking this bug verified. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ka...@chromium.org
, Jun 18 2018