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

Issue 750190 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocked on: View detail
issue 750197
issue 750204
issue 750195

Blocking:
issue 750207



Sign in to add a comment

[meta] Chrome/CrOS Bot prototype

Project Member Reported by rjkroege@chromium.org, Jul 28 2017

Issue description

It would be desirable to setup some machines to validate the idea of running CrOS/Chrome on linux. This configuration would exercise the full Chrome build in an identical manner to how it runs on actual CrOS devices.

See https://docs.google.com/document/d/1XxoMI9hY7YTRQpF5orwl3peZP7putvK80_e2Wh9htus/edit#heading=h.5hegcsd951u4 for details.

 
Blockedon: 750195
Blockedon: 750197
Blockedon: 750204
Blocking: 750207
Cc: kylec...@chromium.org fjhenigman@chromium.org jonr...@chromium.org sky@chromium.org
Components: -Internals>MUS Internals>Services>WindowService
Labels: -Proj-Mustash
Bug scrub: I think the current approach is to run a Chrome OS VM on the waterfall.

Leaving open for now but removing mustash label. Feel free to close / retriage as needed.

Owner: rjkroege@chromium.org
Status: Assigned (was: Available)
This is my understanding from the other bug. I should make sure that this tests ozone/drm code.

rjk: review that the VM tests are adequate.

Sign in to add a comment