Betty-pre-cq: cheets_KeyboardTest failed in VMTest |
||||||||
Issue descriptionbetty-pre-cq VMTest is flaky, sheriffs@, can you please take a look> https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/pre_cq/48956 https://luci-milo.appspot.com/buildbot/chromiumos.tryserver/pre_cq/49074 20:38:09 INFO | autoserv| AUTOTEST_STATUS:: ERROR cheets_KeyboardTest cheets_KeyboardTest timestamp=1502329089 localtime=Aug 09 20:38:09 Timed out waiting for condition: Expected text entered 08/10 14:34:37.398 ERROR| utils:2737| Timed out waiting for condition: Expected text entered 08/10 14:34:37.405 DEBUG| test:0389| Test failed due to Timed out waiting for condition: Expected text entered. Exception log follows the after_iteration_hooks. 08/10 14:34:37.405 DEBUG| test:0392| starting after_iteration_hooks 08/10 14:34:37.408 DEBUG| utils:0212| Running 'logger "autotest finished iteration /usr/local/autotest/results/default/cheets_KeyboardTest/sysinfo/iteration.1"' 08/10 14:34:37.414 WARNI| arc:0402| Iteration 1 failed, taking a screenshot. 08/10 14:34:37.474 WARNI| arc:0410| Unable to capture screenshot. NULL pointer access 08/10 14:34:37.480 DEBUG| test:0395| after_iteration_hooks completed 08/10 14:34:37.481 WARNI| test:0612| The test failed with the following exception Traceback (most recent call last): File "/usr/local/autotest/common_lib/test.py", line 606, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/usr/local/autotest/common_lib/test.py", line 806, in _call_test_function return func(*args, **dargs) File "/usr/local/autotest/common_lib/test.py", line 470, in execute dargs) File "/usr/local/autotest/common_lib/test.py", line 347, in _call_run_once_with_retry postprocess_profiled_run, args, dargs) File "/usr/local/autotest/common_lib/test.py", line 380, in _call_run_once self.run_once(*args, **dargs) File "/usr/local/autotest/tests/cheets_KeyboardTest/cheets_KeyboardTest.py", line 49, in run_once sleep_interval=1) # second File "/usr/local/autotest/common_lib/utils.py", line 2738, in poll_for_condition raise TimeoutError(desc) TimeoutError: Timed out waiting for condition: Expected text entered
,
Aug 10 2017
,
Aug 10 2017
Adding ARC++ Constables. I think there were some talks about race conditions with uinput.
,
Aug 10 2017
Katherine, does maybe someone on your team have insight into why this test is flaky?
,
Aug 10 2017
Adding some people more familiar with this test
,
Aug 10 2017
,
Aug 11 2017
Okay, the story started from https://buganizer.corp.google.com/issues/62209867, which Dan and Nicolas tried to pull in uinput python module and added cros class to work around their issue on soraka. However, the race condition happened as described in https://chromium-review.googlesource.com/c/486560/3/dev-python/python-uinput/files/cros_keys.py#20 where Chrome is not able to be notified at runtime.
,
Aug 11 2017
The following patch tries to use emulated keyboard class in initialize() before Chrome starts. Then when Chrome starts, it will be able to scan and detect the emulated keyboard device from the beginning. https://chrome-internal-review.googlesource.com/#/c/chromeos/autotest-cheets/+/429528/
,
Aug 11 2017
This bug covers the same test, and is older, but doesn't seem to be being worked. https://crbug.com/653048
,
Aug 11 2017
Issue 653048 has been merged into this issue.
,
Aug 12 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/chromeos/autotest-cheets/+/ac5e4c9257650c078a0b27aebf06abf3a8114bb1 commit ac5e4c9257650c078a0b27aebf06abf3a8114bb1 Author: Chung-yih Wang <cywang@google.com> Date: Sat Aug 12 08:26:26 2017
,
Aug 17 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/924c9f348f795c60b97f03bc73d83b8e92e62905 commit 924c9f348f795c60b97f03bc73d83b8e92e62905 Author: Chung-yih Wang <cywang@google.com> Date: Thu Aug 17 08:56:58 2017 input_playback: Fix device matching The patch fixes the device matching with its name as there could be more than two input nodes under the same sysfs device tree. BUG=chromium:754454 TEST=on eve, test_that DUT_IP cheets_KeyboardTest test_that DUT_IP performance_InboxInputLatency Change-Id: Ia9d0fc340f9d816fcfead0eee32b4ae372cfd509 Signed-off-by: Chung-yih Wang <cywang@google.com> Reviewed-on: https://chromium-review.googlesource.com/616623 Commit-Ready: Chung-yih Wang <cywang@chromium.org> Tested-by: Chung-yih Wang <cywang@chromium.org> Reviewed-by: Katherine Threlkeld <kathrelkeld@chromium.org> [modify] https://crrev.com/924c9f348f795c60b97f03bc73d83b8e92e62905/client/cros/input_playback/input_playback.py
,
Feb 5 2018
It looks like we're getting some more flake in this test this weekend.
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned". |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by nxia@chromium.org
, Aug 10 2017