585281 - TEST-UNEXPECTED-FAIL | test-display-issues.js | test_buttons_collapse_and_expand (The collapsy bar should not be shrunk!)

Status: RESOLVED FIXED

(Thunderbird :: Mail Window Front End, defect)

Description

[Mark Banner (:standard8)]

Random orange seen on tinderbox:

TEST-UNEXPECTED-FAIL | e:\buildbot\win32-comm-central-check\build\mail\test\mozmill\quick-filter-bar\test-display-issues.js | test_buttons_collapse_and_expand
  EXCEPTION: The collapsy bar should not be shrunk!
    at: test-display-issues.js line 101
       Error("The collapsy bar should not be shrunk!")  0
       assertExpanded() test-display-issues.js 101
       test_buttons_collapse_and_expand() test-display-issues.js 116
            frame.js 474
            frame.js 530
            frame.js 573
            frame.js 417
            frame.js 579
            server.js 164
            server.js 168

http://tinderbox.mozilla.org/showlog.cgi?log=Thunderbird/1281170291.1281175569.5824.gz#err2

Comment 1

[Andrew Sutherland [:asuth] (he/him)]

Are we sure that the display on the tinderbox is not getting shrunk down to be tiny again by VMware or rdesktop or what not?  That was the problem previously when this happened...

note: logState tries to log the resolution and what not so that I can debug that, but the dump() output is apparently not coming out on the right pipe because it does not show up in the log.

Comment 2

[Mark Banner (:standard8)]

It could be that issue with the screen resolution.

Assigning to gozer - can you check the screen resolution of momo-vm-win2k3-12, as I've not got access to it (jumphost doesn't let me through).

Comment 3

[John Hopkins (:jhopkins)]

I logged in via Terminal Services to the session where buildbot is running.  The screen resolution is 800x600 with 24-bit colour.

Comment 4

[Andrew Sutherland [:asuth] (he/him)]

That is too tiny; the resolution needs to be whatever the docs for the machine setup says... 1280x1024 maybe?

Comment 5

[John Hopkins (:jhopkins)]

All of our win2k3 builders are now at 1280x1024 resolution and screen resolution is monitored by Nagios.  That appears to have resolved this issue as it hasn't occurred recently.