peach_pit-tot-chrome-pfq-informational fails tast.ui.VirtualKeyboardTyping |
|||||
Issue descriptionhttps://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8934138864650306000 tast.ui.VirtualKeyboardTyping: FAIL: Failed to tap "h": got exception: Error: Key "h" not found. No element with aria-label "h". @@@STEP_LINK@[Test-Logs]: tast.ui.VirtualKeyboardTyping: FAIL: Failed to tap "h": got exception: Error: Key "h" not found. No element with aria-label "h".@http://cautotest-prod/tko/retrieve_logs.cgi?job=/results/242890717-chromeos-test/@@@ @@@STEP_LINK@[Test-History]: tast.ui.VirtualKeyboardTyping@https://stainless.corp.google.com/search?test=^tast\.ui\.VirtualKeyboardTyping$&first_date=2018-08-31&last_date=2018-09-28&row=model&col=build&view=matrix@@@ Will return from run_suite with status: ERROR also in veyron_minnie-tot-chrome-pfq-informational https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8934158185670665488
,
Oct 1
shend: Ping. This has been failing pretty frequently since it was added and it affects eve caroline and tricky informationals as well. Can we disable it?
,
Oct 1
,
Oct 1
All the runs of this on -release builders yesterday failed. I see two different error messages: 2018/09/30 07:28:54 [07:28:53.993] Error at virtual_keyboard_typing.go:83: Failed to tap "h": got exception: Error: Key "h" not found. No element with aria-label "h". http://stainless/browse/chromeos-autotest-results/243643433-chromeos-test/ 2018/09/30 07:41:32 [07:41:31.205] Error at virtual_keyboard_typing.go:90: Failed to get the contents of the text field: context deadline exceeded (last error: "!!(document.getElementById('text').value === 'hello tast')" is false) http://stainless/browse/chromeos-autotest-results/243634176-chromeos-test/
,
Oct 1
In the test, we should wait for keyboard buttons to render before trying to tap the UI. I think it should be fixed by https://chromium-review.googlesource.com/c/chromiumos/platform/tast-tests/+/1249403 (trying to get it past CQ), but I'm happy to disable the test if it's causing issues.
,
Oct 2
shend - It's not blocking the PFQ since its informational only, but if your fix doesn't land in a day or two then we should consider disabling it for the time being.
,
Oct 2
Okay thanks. I've been trying to get it past the CQ but it's been flakily failing. Let's give it one more day?
,
Oct 2
one more day SGTM
,
Oct 3
Landed a fix here: https://chromium.googlesource.com/chromiumos/platform/tast-tests/+/d3e93dbe7d307dedb16f34f93d928621d21a400b If it doesn't fix things then we should just disable the test.
,
Oct 3
Thanks for looking into this. I looked at the bots which ran after your fix landed, and they do not seem to have the keyboard tasts failures. But let me wait one more round to verify.
,
Oct 3
Closing as I do not see this anymore. Though after the fix landed im seeing tast.ui.VirtualKeyboardOmnibox failures, not sure if related, and filed issue 891594 for that.
,
Oct 3
Thanks! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by minch@chromium.org
, Sep 28