Closed
Bug 1343580
Opened 8 years ago
Closed 8 years ago
Black screenshots and small screen resolution on Windows 10 test jobs
Categories
(Infrastructure & Operations :: RelOps: General, task)
Infrastructure & Operations
RelOps: General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: pmoore, Unassigned)
References
Details
Extracted from https://bugzilla.mozilla.org/show_bug.cgi?id=1326420#c0:
> looking at screenshots I just see a black image, I am not sure if that is another issue, or something with the win10 UI.
Reporter | ||
Comment 1•8 years ago
|
||
Probably (but not definitely) caused by bug 1343582.
Comment 2•8 years ago
|
||
FWIW the screenshot program we use to generate those just calls `GetDesktopWindow()` then blits that to a bitmap:
https://dxr.mozilla.org/mozilla-central/rev/e1135c6fdc9bcd80d38f7285b269e030716dcb72/testing/tools/screenshot/win32-screenshot.cpp#90
Comment 3•8 years ago
|
||
Pete, just wanted to get back to you on checking win 7 and can confirm that screenshots on win 7 are working fine.
Comment 5•8 years ago
|
||
The gpu test jobs [1] are failing with:
> 60 INFO TEST-UNEXPECTED-FAIL | gfx/tests/mochitest/test_acceleration.html | Acceleration enabled on Windows XP or newer - didn't expect +0, but got it
This is the same as bug 1090643.
This got fixed on bug 1190868#c8.
Original script [2]
[1] https://treeherder.mozilla.org/#/jobs?repo=try&author=armenzg@mozilla.com&filter-searchStr=windows10-64%20gpu&selectedJob=87557961
[2] https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/external_tools/mouse_and_screen_resolution.py?q=mouse_and_screen_resolution.py&redirect_type=direct
Blocks: 1326419
Summary: Black screenshots in win10 tests → Black screenshots and small screen resolution on Windows 10 test jobs
Reporter | ||
Comment 6•8 years ago
|
||
Fixed in generic worker 8.3.0!
See win10 screenshot:
* https://public-artifacts.taskcluster.net/X4CZTXqWToadLs3X1SOdEA/0/public/test_info/mozilla-test-fail-screenshot_sadien.png
8.3.0 currently includes a fix for bug bug depends on bug 1358142 which has just landed on mozilla-inbound - so before we can roll out 8.3.0 to all workers in production, we'll need to wait for bug 1358142 to reach all branches where windows tests run on taskcluster in generic-worker.
In the meantime, try pushes can be made that use the new generic-worker, if you use the gecko-1-t-win10-64-beta worker type instead of the gecko-1-t-win10-64 worker type. This change can be made directly in the try push. Note, you'll also need the fix from bug 1358142 in your try push too. If you need the capacity of the worker type scaled up (I think maxCapacity is pretty low normally) then ping someone in the taskcluster team. Hopefully in the next day or so the mozharness fix will have rolled out far enough that we can upgrade generic-worker to 8.3.0 on all worker types, and you won't need to use the beta worker type at all. This is just a workaround for anyone desperate to try something out immediately.
Reporter | ||
Comment 7•8 years ago
|
||
This has been rolled out globally to win10 worker types now, so closing. No workaround needed any more.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•