Closed Bug 974911 Opened 11 years ago Closed 11 years ago

figure out why test machines can't set resolution sometimes

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task, P3)

Product:
Infrastructure & Operations Graveyard
Component:
CIDuty
Platform:
x86_64
macOS
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: bhearsum, Assigned: kmoir)

Details

From bug 974485: (In reply to Ben Hearsum [:bhearsum] from comment #0) > Can't set resolution correctly: > Feb 19 09:42:23 talos-r4-snow-065 puppet-agent[740]: > (/Stage[main]/Screenresolution/Exec[set-resolution]/returns) 2014-02-19 > 09:42:23.662 screenresolution[1269:903] Error: mode 1600x1200x32 not > available on display 0 > Feb 19 09:42:23 talos-r4-snow-065 puppet-agent[740]: > /usr/local/bin/screenresolution set 1600x1200x32 returned 1 instead of one > of [0] (In reply to (Wed-Thu. Feb.19-20th in TRIBE) Armen Zambrano [:armenzg] (Release Engineering) (EDT/UTC-4) from comment #1) > Some of these machines report few puppet error and then recover.
OS: Linux → Mac OS X
Assignee: nobody → kmoir
Priority: -- → P3
I looked at this for a while this afternoon and couldn't figure out the root of this intermitten problem. Will look at it again after I write a patch for another bug.
Does this still happen?
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.