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

Issue 910980 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Dec 3
Cc:
█ kbr@chromium.org
bsheedy@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

WebXrVrBrowserTestStandard.TestPresentationPoses runs on win7_chromium_rel_ng builder, but it is disabled

Project Member Reported by tikuta@chromium.org, Dec 3 
Why do we run disabled test on win7_chromium_rel_ng builder?

https://ci.chromium.org/p/chromium/builders/luci.chromium.try/win7_chromium_rel_ng/142834

gtest_also_run_disabled_tests is looks originally come from
https://chromium.googlesource.com/chromium/src/+/dfd27eaeab7c2489ca72769d3a964f2a7ec68002

Comment 1 by bsheedy@chromium.org, Dec 3 

The running of disabled tests is a hack. Most VR tests have fairly strict GPU requirements (DirectX 11.1 support), so there are only a handful of machines they can actually run on. So, by default, they're disabled, and we pass --gtest_also_run_disabled_tests with a specific test filter that should only pick up the VR tests.

Comment 2 by tikuta@chromium.org, Dec 3

Status: WontFix (was: Untriaged)
I see. And the flakiness of the test seems disappeared. Let me mark this as WontFix.
►

Sign in to add a comment