1326420 - Windows 10 test jobs on Taskcluster are failing printer related tests

Status: RESOLVED FIXED

(Infrastructure & Operations :: RelOps: General, task)

Description

[Joel Maher ( :jmaher ) (UTC -8)]

I am not sure what is required, but maybe of the failing tests on win10 are related to printers not being installed or available.  Possibly there is a default print to file or a dummy printer that we expect.

I imagine looking on win7 and comparing to win10 would give us an idea.  Many of the bc* failures are printer related:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=e762cd858e7055fdb542480c3ef8734f6f3c5801&filter-tier=1&filter-tier=2&filter-tier=3&selectedJob=65491628&filter-searchStr=tc%20x64

looking at screenshots I just see a black image, I am not sure if that is another issue, or something with the win10 UI.

Comment 1

[Armen [:armenzg]]

Hey Rob, what is the state of this? I'm trying to get the context and where we stand. Thanks!

Comment 2

[Rob Thijssen [:grenade (EET/UTC+0300)]]

:pmoore is dealing with the screenshots issue in the bug linked above. i believe that is a problem with an upstream lib we use for process isolation.
the printer driver failures is in my queue although win 10 has taken a back seat to win 7 recently. i should be able to look at it next week.

Comment 3

[Greg Arndt [:garndt]]

Have the printer drivers landed in the new images being used? If so, is this still failing for the same reason?

Comment 4

[Greg Arndt [:garndt]]

If I recall correctly, Rob explained that we have never installed any special printer drivers in our windows environments so there is nothing to do for the environment here.  If tests require something that Windows 10 no longer provides over previous Windows installations, we need to be told what that might be or tests might need to be reworked to work with windows 10.

Comment 5

[Joel Maher ( :jmaher ) (UTC -8)]

can we have a list of what possible print options there are on windows 7?  In many cases there is a default print to file or pdf- possibly we are missing that in windows 10?

Comment 6

[Rob Thijssen [:grenade (EET/UTC+0300)]]

printer list checked using custom tasks:
- win7: https://tools.taskcluster.net/task-inspector/#fgneYZbnTmKqDOT8N9HRRA/
- win10: https://tools.taskcluster.net/task-inspector/#faZqL2CiTOSalKd7EnjLVQ/

Windows 7:
  from: https://public-artifacts.taskcluster.net/fgneYZbnTmKqDOT8N9HRRA/0/public/logs/live_backing.log
  - Microsoft XPS Document Writer
  - Fax

Windows 10:
  from: https://public-artifacts.taskcluster.net/faZqL2CiTOSalKd7EnjLVQ/0/public/logs/live_backing.log
  - Microsoft XPS Document Writer
  - Microsoft Print to PDF
  - Fax

Comment 7

[Joel Maher ( :jmaher ) (UTC -8)]

looking at a push I did last night:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=08f6c9e2c0a68a96500ce0d20544fbbea280da3c

bc6 fails in toolkit/components/printing/tests/browser_page_change_print_original.js, and I see this error:
23:20:05     INFO -  738 INFO Console message: [JavaScript Error: "[Exception... "Component returned failure code: 0x80480001 (NS_ERROR_GFX_PRINTER_NO_PRINTER_AVAILABLE) [nsIWebBrowserPrint.printPreview]"  nsresult: "0x80480001 (NS_ERROR_GFX_PRINTER_NO_PRINTER_AVAILABLE)"  location: "JS frame :: chrome://global/content/browser-content.js :: enterPrintPreview/< :: line 662"  data: no]"]
23:20:05     INFO -  enterPrintPreview/<@chrome://global/content/browser-content.js:662:11


in addition bc1 fails in test browser/base/content/test/tabs/browser_tabSwitchPrintPreview.js and I see this error:
23:14:57     INFO -  267 INFO Console message: [JavaScript Error: "[Exception... "Component returned failure code: 0x80480001 (NS_ERROR_GFX_PRINTER_NO_PRINTER_AVAILABLE) [nsIWebBrowserPrint.printPreview]"  nsresult: "0x80480001 (NS_ERROR_GFX_PRINTER_NO_PRINTER_AVAILABLE)"  location: "JS frame :: chrome://global/content/browser-content.js :: enterPrintPreview/< :: line 662"  data: no]"]


and this looks to be the same error message:
https://dxr.mozilla.org/mozilla-central/source/toolkit/content/browser-content.js#662


I have verified on my local win10 laptop that these tests pass, so this is something unique in the test environment.

Comment 8

[Joel Maher ( :jmaher ) (UTC -8)]

running on the new IX win10 machines, I can get this test to pass, all signs  are leading towards an issue with the win10 image we are using.  As a note, both the win10 ix machine and my local machine are running windows 10 build 1703.

On the win10-ix machine I see:
Fax
Microsoft print to PDF
Microsoft XPS document writer


and in the settings, the "let windows manage my default printer" is checked.

Comment 9

[Rob Thijssen [:grenade (EET/UTC+0300)]]

i'm just guessing but maybe a user issue? Joel, when you ran this test successfully on IX win 10, were you logged in as Administrator by any chance?

Comment 10

[Joel Maher ( :jmaher ) (UTC -8)]

good question- I am not sure to be honest, it could have been a user that had admin privileges.  

I am not able to get a win10 loaner to work, possibly you would have better luck with one of the new win10 machines?

Comment 11

[Greg Arndt [:garndt]]

I attempted to run the bc6 tests in a loaner, but I received an error for a different failure and not the printing one.  I'm really unsure if I'm running this in a different way than what the tests expect or something.

Help definitely appreciate with figuring out where to go with this.  I think we've hit a wall.

Comment 12

[Joel Maher ( :jmaher ) (UTC -8)]

I think this might be fixed- I don't see these tests failing on a try run:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=53fa35b98b8a48fac2252a9e5a1f556547e6e4e9&filter-searchStr=browser-chrome+win

there are 4 failures (same test fails twice in two different modes):
browser/base/content/test/contextMenu/browser_contextmenu_touch.js (a win10 specific test - passes for me locally)
browser/base/content/test/touch/browser_menu_touch.js (a win10 specific test - fails for me locally)
browser/components/extensions/test/browser/browser_ext_user_events.js (run in two different modes)

fixing these 3 tests will yield green browser-chrome runs, likewise we could consider running these on win10-ix (hardware via BBB), or disabling the tests for win10 only)

Comment 13

[Joel Maher ( :jmaher ) (UTC -8)]

:grenade do you have thoughts here, should we close this bug and open new bugs for the above mentioned tests?

Comment 14

[Joel Maher ( :jmaher ) (UTC -8)]

I have filed 3 bugs to track each of these test cases, closing this out for now.