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

Issue 776908 link

Starred by 2 users
Status: Assigned
Owner:
█ vollick@chromium.org
Last visit > 30 days ago
Cc:
█ vollick@chromium.org
cjgrant@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug
Proj-XR

Blocked on:
issue 767282

Show other hotlists

Hotlists containing this issue:
VR-Automated-Tests


Sign in to add a comment

VR: Add tests for asynchronous DrawFrame and related control flows.

Project Member Reported by mthiesse@chromium.org, Oct 20 2017 
See https://chromium-review.googlesource.com/c/chromium/src/+/721577/4

When we refactor vr_shell_gl to be more modular and function on desktop or with emulated VR devices, we should add tests that exercise all possible orderings of frames arriving and callbacks running for our drawing path to ensure we don't add new races.

Comment 1 by vollick@chromium.org, Oct 20 2017

Blockedon: 767282

Comment 2 by ymalik@chromium.org, Feb 5 2018

Labels: -Pri-1 -M-66 M-67 Pri-2
Owner: vollick@chromium.org
@Ian, assigning this to you as the refactoring bug is owned by you. Lowering the priority and changing the target milestone though as I don't think there's active work on it.

Comment 3 by cjgrant@chromium.org, May 15 2018

Labels: -M-67
Removing M-67 milestone during a triage sweep with ericde@.  A milestone should be reassigned when the issue is in scope.

Comment 4 by btebbs@chromium.org, Jul 4

Components: Internals>XR

Comment 5 by ddorwin@chromium.org, Jul 16 

vollick, should this be assigned to you or available?

Comment 6 by benhenry@chromium.org, Aug 2

Status: Assigned (was: Available)

Comment 7 by efoo@chromium.org, Aug 7 

Removing Internals>VR component and remapping to Internals>XR

Comment 8 by efoo@chromium.org, Aug 7

Components: -Internals>VR
►

Sign in to add a comment