Closed
Bug 776604
Opened 12 years ago
Closed 12 years ago
install and and run screenresolution dmg on puppetAgain Darwin slave
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kmoir, Assigned: kmoir)
References
Details
Attachments
(3 files, 1 obsolete file)
(deleted),
patch
|
dustin
:
review+
|
Details | Diff | Splinter Review |
(deleted),
patch
|
dustin
:
review+
kmoir
:
checked-in+
|
Details | Diff | Splinter Review |
(deleted),
patch
|
dustin
:
review+
kmoir
:
checked-in+
|
Details | Diff | Splinter Review |
I've created a new dmg for 10.8 which I've copied to /data and will attach a patch for the changes I've tested.
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → kmoir
Assignee | ||
Comment 1•12 years ago
|
||
I also added minimal changes to the builder.pp class to support this, there are more changes forthcoming to this class. I'm trying to create smaller patches so they are easier for reviewers to parse.
Attachment #644990 -
Flags: review?(dustin)
Assignee | ||
Comment 2•12 years ago
|
||
I should have mentioned that I built the dmg from the source here
git://github.com/jhford/screenresolution.git
Comment 3•12 years ago
|
||
Comment on attachment 644990 [details] [diff] [review]
patch
My only complaint here is that there's no docs or shell-script on how the screenresolution DMG was made, so if I needed to re-create it for a new version, or if Apple decides to switch CPUs again, I'm at a loss.
I'd like to get this user stuff settled once and for all - it's causing a lot of churn both in your patches and mine. So I'll open a new bug, but for now anything goes to get the other patches working :)
So, r+ conditioned on the addition of a shell script that builds the DMG. It looks like that may be as simple as downloading a tag from github (I don't see 1.6 there?) and running 'make dmg', but such a script both documents those simple steps (I had no idea where the source was until I just asked in IRC) and provides a basis for future, possibly more complicated approaches (e.g., at some point we may want to install in /tools and link, like the other custom packages).
Attachment #644990 -
Flags: review?(dustin) → review+
Assignee | ||
Comment 4•12 years ago
|
||
Assignee | ||
Updated•12 years ago
|
Attachment #645083 -
Flags: checked-in+
Updated•12 years ago
|
Attachment #645083 -
Flags: review+
Assignee | ||
Comment 5•12 years ago
|
||
Documented here https://wiki.mozilla.org/ReleaseEngineering/PuppetAgain/Modules/packages#packages::mozilla::screenresolution
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Comment 6•12 years ago
|
||
Now that the other user stuff is working, I'm seeing
err: /Stage[main]/Users::Builder/Exec[verify-resolution]/returns: change from notrun to 0 failed: /usr/local/bin/screenresolution set 1280x1024x32 returned 1 instead of one of [0] at /etc/puppet/environments/dmitchell/env/modules/users/manifests/builder.pp:119
bash-3.2# /usr/local/bin/screenresolution set 1280x1024x32
2012-07-26 10:15:30.770 screenresolution[6260:707] starting screenresolution argv=/usr/local/bin/screenresolution set 1280x1024x32
2012-07-26 10:15:30.775 screenresolution[6260:707] Error: the mode '1280x1024x32' couldn't be parsed
bash-3.2# /usr/local/bin/screenresolution get
2012-07-26 10:15:39.656 screenresolution[6261:707] starting screenresolution argv=/usr/local/bin/screenresolution get
2012-07-26 10:15:39.661 screenresolution[6261:707] Display 0: 1600x1200x32@60
bash-3.2# /usr/local/bin/screenresolution set 1280x1024x32@60
2012-07-26 10:15:47.001 screenresolution[6262:707] starting screenresolution argv=/usr/local/bin/screenresolution set 1280x1024x32@60
2012-07-26 10:15:47.006 screenresolution[6262:707] set mode on display 0 to 1280x1024x32@60
So maybe the required string is different?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 7•12 years ago
|
||
Yes, I saw that yesterday too. The default resolution is 1600x1200x32@60. Not sure what it should be for the tests to run correctly, I'll ask.
Assignee | ||
Comment 8•12 years ago
|
||
Attachment #646263 -
Flags: review?(dustin)
Comment 9•12 years ago
|
||
Comment on attachment 646263 [details] [diff] [review]
patch for default resolution
bash-3.2# /usr/local/bin/screenresolution set 1600x1200x32
2012-07-26 12:50:52.245 screenresolution[1012:707] starting screenresolution argv=/usr/local/bin/screenresolution set 1600x1200x32
2012-07-26 12:50:52.250 screenresolution[1012:707] Error: the mode '1600x1200x32' couldn't be parsed
I don't think the resolution is the problem. I think the problem is the missing refresh rate.
Attachment #646263 -
Flags: review?(dustin) → review-
Assignee | ||
Comment 10•12 years ago
|
||
fix for this as well as a running tidy to clean up active state on Darwin
Attachment #646263 -
Attachment is obsolete: true
Attachment #646298 -
Flags: review?(dustin)
Comment 11•12 years ago
|
||
Comment on attachment 646298 [details] [diff] [review]
patch
I'm not generally a fan of piggybacking unrelated changes together, but I'll let it slide this time ;)
Attachment #646298 -
Flags: review?(dustin) → review+
Assignee | ||
Updated•12 years ago
|
Attachment #646298 -
Flags: checked-in+
Assignee | ||
Comment 12•12 years ago
|
||
Fixed #2
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
Updated•6 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•