New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 617066 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug
Team-Accessibility



Sign in to add a comment

Some WebUITests flakily failing for accessibility reasons

Project Member Reported by vabr@chromium.org, Jun 3 2016

Issue description

Build: https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%281%29/builds/53336

Failed tests:
AdvancedSettingsWebUITest.testAdvancedSettingsShown
AutofillOptionsWebUITest.testOpenAutofillOptions

Logs attached, the core message is the same:
Error:
Accessibility issues found on chrome://settings-frame/autofill
*** Begin accessibility audit results ***
An accessibility audit found
Errors:
Error: AX_ARIA_08 (Elements with ARIA roles must ensure required owned elements are present) failed on the following elements (1 - 2 of 2):
#default-search-engine-list
#other-search-engine-list
See https://github.com/GoogleChrome/accessibility-developer-tools/wiki/Audit-Rules#ax_aria_08 for more information.
*** End accessibility audit results ***
    at Object.runAccessibilityAudit (test_api.js:371:17)
    at Object.runAccessibilityAudit (test_api.js:501:22)
    at test_api.js:995:20
    at testDone (test_api.js:783:31)
    at runTest (test_api.js:1042:7)
    at <anonymous>:1:1
  Actual: false
Expected: true
[136:3104:0603/000932:ERROR:gles2_cmd_decoder.cc(15072)] [.DisplayCompositor-0D8168B0]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[136:3104:0603/000932:ERROR:gles2_cmd_decoder.cc(8253)] [.DisplayCompositor-0D8168B0]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
 
Log File contents.html
429 KB View Download

Comment 1 by vabr@chromium.org, Jun 3 2016

Components: UI>Accessibility UI>Settings
Summary: Some WebUITests flakily failing for accessibility reasons (was: Some autofill-related WebUITests failing for accessibility reasons)
This is actually not autofill-specific, also other tests have a similar issues, e.g., in https://build.chromium.org/p/chromium.win/builders/Win7%20Tests%20%281%29/builds/53327, SettingsFormatWebUITest.RadioButtonNameValueCheck failed with this message:

[ RUN      ] SettingsFormatWebUITest.RadioButtonNameValueCheck
[5772:5432:0602/182933:WARNING:CONSOLE(0)] "/deep/ combinator is deprecated. See https://www.chromestatus.com/features/6750456638341120 for more details.", source:  (0)
[5772:5432:0602/182934:INFO:CONSOLE(1196)] "Running TestCase SettingsFormatWebUITest.RadioButtonNameValueCheck", source: test_api.js (1196)
[5772:5432:0602/182934:ERROR:web_ui_test_handler.cc(76)] Failed: RUN_TEST_F("SettingsFormatWebUITest","RadioButtonNameValueCheck")
Error:
Accessibility issues found on chrome://settings-frame/
*** Begin accessibility audit results ***
An accessibility audit found
Errors:
Error: AX_ARIA_08 (Elements with ARIA roles must ensure required owned elements are present) failed on the following elements (1 - 2 of 2):
#default-search-engine-list
#other-search-engine-list
See https://github.com/GoogleChrome/accessibility-developer-tools/wiki/Audit-Rules#ax_aria_08 for more information.


*** End accessibility audit results ***
    at Object.runAccessibilityAudit (test_api.js:371:17)
    at Object.runAccessibilityAudit (test_api.js:501:22)
    at test_api.js:995:20
    at testDone (test_api.js:783:31)
    at runTest (test_api.js:1042:7)
    at <anonymous>:1:1
  Actual: false
Expected: true
[  FAILED  ] SettingsFormatWebUITest.RadioButtonNameValueCheck, where TypeParam =  and GetParam() =  (2434 ms)
Project Member

Comment 2 by bugdroid1@chromium.org, Jun 3 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/e7e37202cb9adb6e036acc5c8aa54697c10162c2

commit e7e37202cb9adb6e036acc5c8aa54697c10162c2
Author: vabr <vabr@chromium.org>
Date: Fri Jun 03 08:55:03 2016

Disable some flaky WebUI tests on Win

These tests:
AdvancedSettingsWebUITest.testAdvancedSettingsShown
AutofillOptionsWebUITest.testOpenAutofillOptions

More info on the bug.

TBR=mathp@chromium.org, estade@chromium.org
BUG= 617066 

Review-Url: https://codereview.chromium.org/2036753003
Cr-Commit-Position: refs/heads/master@{#397668}

[modify] https://crrev.com/e7e37202cb9adb6e036acc5c8aa54697c10162c2/chrome/browser/ui/webui/options/autofill_options_browsertest.js
[modify] https://crrev.com/e7e37202cb9adb6e036acc5c8aa54697c10162c2/chrome/browser/ui/webui/options/browser_options_browsertest.js

Project Member

Comment 3 by sheriffbot@chromium.org, Jul 7 2016

Labels: -M-53 M-54 MovedFrom-53
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: NewComponent-Accessibility-Browser
Labels: NewComponent-Accessibility
Labels: NewComponent-Accessibility-Internals
Components: Internals>Accessibility
Components: -UI>Accessibility
Labels: -newcomponent-accessibility-internals -newcomponent-accessibility
Labels: -newcomponent-accessibility-browser
Cc: hcarmona@chromium.org quacht@google.com
Labels: triage-dominic
Labels: triage-dominic-internals
Labels: -triage-dominic -triage-dominic-internals
Labels: -M-54 -MovedFrom-53
Owner: hcarmona@chromium.org
Status: Assigned (was: Untriaged)
Status: WontFix (was: Assigned)
This is about tests that no longer exist. Won't Fix.
Components: Tests>Disabled
Labels: Test-Disabled

Sign in to add a comment