Closed Bug 753000 Opened 11 years ago Closed 11 years ago
Windows 7 (32 & 64 bit) unit test builders have inconsistent display resolution to other windows builders and to the set-up scripts
According to http://hg.mozilla.org/build/puppet-manifests/annotate/a2a258487085/modules/buildslave/files/startTalos-w7.bat#l10 http://hg.mozilla.org/build/puppet-manifests/annotate/a2a258487085/modules/buildslave/files/startTalos-w764.bat#l11 the builders are meant to have 1280 x 1024 resolution. However, on the Thunderbird comm-central builders we're seeing MozMill test failures that are typically a result of having the screen resolution set wrong (we require 1280x1024). According to bhearsum, talos-r3-w7-066 and t-r3-w764-003 appear to be on a 800 x 600 resolution, or maybe a 1024 x 768. Hence it looks like the configuration hasn't been applied.
Armen, any idea about this?
Component: Release Engineering → Release Engineering: Platform Support
QA Contact: release → coop
At some point we upgraded the stock drivers which caused a regression on the available screen resolutions. The only way to fix this is by attaching a dongle to the machine. I still have to test the path out of this situation. My ideal solution is: 1) replace those start scripts to set a 800x600 resolution (make sure no regressions are caused) 2) take down slaves and attach dongles (the screen resolution should still be 800x600 because of #1) 3) find a way to control screen resolution by code; this way we can control it by branch If we could do #3 directly we would not need #2 & #1. I think. Unfortunately, even the mouse pointer and focus gets on the way depending on the screen resolution. You can read for more context from here on: https://bugzilla.mozilla.org/show_bug.cgi?id=712630#c74 What should we do to this bug? Block it on bug 712630? or mark it as a dupe?
(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #2) > What should we do to this bug? Block it on bug 712630? or mark it as a dupe? I'm happy with either. If we dupe it, then I think we should re-title that bug and move it to releng, as that seems to be where the work is currently.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Ok, now bug 712630 has landed, I'm going to use this bug to do the necessary work in Thunderbird land to get the screen resolution right for us.
Status: RESOLVED → REOPENED
Component: Release Engineering: Platform Support → Testing Infrastructure
Product: mozilla.org → Thunderbird
QA Contact: coop → testing-infrastructure
Resolution: DUPLICATE → ---
Version: other → Trunk
The MozMill tests (test-display-issues.js) have required a screen resolution of 1280 x 1024. When we moved to the Firefox infrastructure the Windows 7 builders were set on 1024 x 768 and the Windows XP ones on 1280 x 1024. Due to this, the Windows 7 MozMill builders have been on permanent orange since we moved to the new infra. This patch takes the work one in bug 712630 and applies it to us - to use 1280 x 1024 on our builders. It also adds a couple of comments to test-display-issues.js so that it reminds us better (we've discussed in the past about detecting the screen res, but iirc we don't have the tools easily available in mozmill tests, and that would be a separate bug anyway ;-) ). As you can't test the patch locally, I've already had this on try server, you can see the results here: https://tbpl.mozilla.org/?tree=Thunderbird-Try&noignore=1&rev=56649865b138 (the noignore=1 is so you can see the currently hidden builders)
Assignee: nobody → mbanner
Status: REOPENED → ASSIGNED
Attachment #637612 - Flags: review?(irving)
Comment on attachment 637612 [details] [diff] [review] The fix Review of attachment 637612 [details] [diff] [review]: ----------------------------------------------------------------- Try build looks good, change looks good.
Attachment #637612 - Flags: review?(irving) → review+
Status: ASSIGNED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → Thunderbird 16.0
You need to log in before you can comment on or make changes to this bug.