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

Issue 704621 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Jul 25
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

display_Resolution.* failing/erroring on samus

Project Member Reported by rjahagir@chromium.org, Mar 23 2017

Issue description

Samus errors out on display_Resolution.mirrored (Failure to set_mirrored) and fails on display_Resolution.extended, on both samus devices deployed in lab. Has been failing since R58-9290.0.0

Error [display_Resolution.mirrored]: 
Failure to set_mirrored(True)

Failure [display_Resolution.extended]: 
Screen size (1024, 768) is not as expected (1920, 1080)!; Detected mis-matched resolutions: CrOS (1024, 768); Chameleon (1024, 768); Expected (1280, 800).; Screen size (1024, 768) is not as expected (1680, 1050)!; Screen size (1024, 768) is not as expected (1600, 900)!; Detected mis-matched resolutions: CrOS (1024, 768); Chameleon (1024, 768); Expected (1600, 900).; Screen size (1024, 768) is not as expected (1440, 900)!; Detected mis-matched resolutions: CrOS (1024, 768); Chameleon (1024, 768); Expected (1280, 720).; Screen size (1024, 768) is not as expected (1280, 720)!; Detected mis-matched resolutions: CrOS (1024, 768); Chameleon (1024, 768); Expected (1680, 1050).; Screen size (1024, 768) is not as expected (1280, 800)!; Detected mis-matched resolutions: CrOS (1024, 768); Chameleon (1024, 768); Expected (1920, 1080).; Detected mis-matched resolutions: CrOS (1024, 768); Chameleon (1024, 768); Expected (1440, 900).


Can this be manually reproduced? 
 
Status: Archived (was: Untriaged)

Sign in to add a comment