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

Issue 698030 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Jul 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature

Blocked on:
issue 620927



Sign in to add a comment

[meta] mus_ws_unittests should not use mus-gpu

Project Member Reported by fsam...@chromium.org, Mar 2 2017

Issue description

Window server unit tests should be isolated to the window server. We should identify all interfaces that we need to mock out to make this happen.

This basically means WindowServer and service.cc should not start up ozone or Gpu or display compositor when in test mode.

Perhaps we can also split mus_ws_unittests into two binaries: one binary for the window server API and one for window server internals.
 
Status: Available (was: Untriaged)
Labels: Type-Feature
Owner: sadrul@chromium.org
Status: Assigned (was: Available)
Assigning to sadrul for triage since this involves mocking out the gpu interface. 
Cc: weiliangc@chromium.org
Blockedon: 620927
This will be easier once the process split happens.
Cc: varkha@chromium.org
Blocking: -601863
Components: -Internals>MUS
Is this obsolete?
Status: WontFix (was: Assigned)
I think it is.

Sign in to add a comment