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

Issue 728186 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Factory: Allow aquarium_webgl to run in full screen.

Project Member Reported by hungte@chromium.org, May 31 2017

Issue description

This is a request from partners.

Some projects may want to run RRT or LTOS using factory software for a very long time, for example 24x7 hours. The static elements of factory UI will cause burn-in on LCD panel.

One possible solution is to enable screen saver, but for stress testing we do want to test graphics (aquarium_webgl). So  the better approach is to allow running aquarium_webgl pytest in full screen mode.
 

Comment 1 by hungte@chromium.org, May 31 2017

Cc: stimim@chromium.org
Owner: petershih@chromium.org
Status: Assigned (was: Untriaged)
+petershih

Hi Peter, maybe you can try this?

Let me know if you are not available.
Status: Started (was: Assigned)
Starts now: https://chromium-review.googlesource.com/c/569941/
Project Member

Comment 3 by bugdroid1@chromium.org, Jul 27 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/factory/+/02f259c021eb38e7591a62580c5db93400724f0d

commit 02f259c021eb38e7591a62580c5db93400724f0d
Author: Shen-En Shih <petershih@chromium.org>
Date: Thu Jul 27 05:41:57 2017

Aquarium - A button to toggle full screen

In run-in test, a webgl-based aquarium is used to test the
graphics. In a a long-running run-in test, the static parts
of our goofy UI might cause a burn-in on the LCD panel.

A button is added to the aquairum iframe, which can be used
to toggle full screen mode.

By default, it goes to full screen mode when the tests starts.

BUG= chromium:728186 
TEST=manually

Change-Id: I52de045a7fd88473b73d1fc89cc5f8e3fd39a6af
Reviewed-on: https://chromium-review.googlesource.com/569941
Commit-Ready: Shen-En Shih <petershih@chromium.org>
Tested-by: Shen-En Shih <petershih@chromium.org>
Reviewed-by: Hung-Te Lin <hungte@chromium.org>

[modify] https://crrev.com/02f259c021eb38e7591a62580c5db93400724f0d/py/test/test_lists/generic_run_in.py
[modify] https://crrev.com/02f259c021eb38e7591a62580c5db93400724f0d/py/test/pytests/webgl_aquarium.py
[add] https://crrev.com/02f259c021eb38e7591a62580c5db93400724f0d/py/test/pytests/webgl_aquarium_static/goofy_webgl_aquarium.css

Comment 4 by hungte@chromium.org, Jul 27 2017

Status: Verified (was: Started)
Project Member

Comment 5 by bugdroid1@chromium.org, Nov 8 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/factory/+/358fd3be5e0ef3a411e778bbd1572181e7f6cfc1

commit 358fd3be5e0ef3a411e778bbd1572181e7f6cfc1
Author: Hung-Te Lin <hungte@chromium.org>
Date: Wed Nov 08 16:28:38 2017

pytests: webgl_aquarium: Move fpsContainer in full screen to prevent burn-in.

The webgl_aquarium in full screen mode should have every pixel keep
changing to prevent screen burn-in, but currently there are two elements
displaying fixed messages: the FPS container (with timer, toggle button
and FPS) and info.

Revised Javascript and keep moving fpsContainer so it's in different
locations over time when in full screen mode.

BUG= chromium:728186 
TEST=manual test

Change-Id: Iecb72981af0661516a28798692a10cac27644775
Reviewed-on: https://chromium-review.googlesource.com/757994
Commit-Ready: Hung-Te Lin <hungte@chromium.org>
Tested-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Pi-Hsun Shih <pihsun@chromium.org>

[modify] https://crrev.com/358fd3be5e0ef3a411e778bbd1572181e7f6cfc1/py/test/pytests/webgl_aquarium.py

Sign in to add a comment