1364517 - notification-related tests fail on windows 10

Status: RESOLVED INVALID

(Toolkit Graveyard :: Notifications and Alerts, defect)

Description

[Dustin J. Mitchell [:dustin] (he/him)]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=3be4aeca4e49186a5608d661562305fdb0ad534c&exclusion_profile=false&group_state=expanded&filter-searchStr=mochitest-5&selectedJob=97755397

18:27:03     INFO -  968 INFO TEST-START | toolkit/components/alerts/test/test_alerts.html
18:27:03     INFO -  GECKO(5476) | ++DOMWINDOW == 21 (000001EE0C488800) [pid = 5476] [serial = 21] [outer = 000001EE0C173000]
18:27:04     INFO -  GECKO(5476) | ++DOMWINDOW == 22 (000001EE0C8D1800) [pid = 5476] [serial = 22] [outer = 000001EE0C173000]
18:27:04     INFO -  GECKO(5476) | MEMORY STAT | vsize 1736MB | vsizeMaxContiguous 132152756MB | residentFast 298MB | heapAllocated 130MB
18:27:04     INFO -  969 INFO TEST-OK | toolkit/components/alerts/test/test_alerts.html | took 1281ms
18:27:04     INFO -  TEST-INFO | started process screenshot
18:27:04     INFO -  TEST-INFO | screenshot: exit 0
18:27:04    ERROR -  970 INFO TEST-UNEXPECTED-FAIL | toolkit/components/alerts/test/test_alerts.html | showAlertNotification() succeeded.  Waiting for notification... - Result logged after SimpleTest.finish()

https://public-artifacts.taskcluster.net/GLHTzND0SiyoyZTHBG-F5Q/0/public/test_info/mozilla-test-fail-screenshot_yt0bty.png (save you a click: shows no notifications..)

Are notifications different on Windows 10 and Windows 7?

This is part of ongoing, aggressive efforts to green up tests on Windows 10, so any assistance would be appreciated!  ni?MattN based on lots of r? for this file in the hg history -- please feel free to redirect me!

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

I'm guessing these are related, but if not can be split out into new bugs:

18:27:16    ERROR -  996 INFO TEST-UNEXPECTED-FAIL | toolkit/components/alerts/test/test_principal.html | Should include source for node principal - got undefined, expected "via mochi.test:8888"
18:27:16     INFO -      SimpleTest.is@SimpleTest/SimpleTest.js:312:5
18:27:16     INFO -      testNodePrincipal@toolkit/components/alerts/test/test_principal.html:92:3
18:27:16     INFO -      onFulfilled@SimpleTest/SpawnTask.js:69:15
18:27:16     INFO -      promise callback*next@SimpleTest/SpawnTask.js:104:45
18:27:16     INFO -      onFulfilled@SimpleTest/SpawnTask.js:73:7
18:27:16     INFO -      co/<@SimpleTest/SpawnTask.js:58:5
18:27:16     INFO -      co@SimpleTest/SpawnTask.js:54:10
18:27:16     INFO -      toPromise@SimpleTest/SpawnTask.js:122:60
18:27:16     INFO -      next@SimpleTest/SpawnTask.js:103:19
18:27:16     INFO -      promise callback*next@SimpleTest/SpawnTask.js:104:45
18:27:16     INFO -      promise callback*next@SimpleTest/SpawnTask.js:104:45
18:27:16     INFO -      promise callback*next@SimpleTest/SpawnTask.js:104:45
18:27:16     INFO -      onFulfilled@SimpleTest/SpawnTask.js:73:7
18:27:16     INFO -      co/<@SimpleTest/SpawnTask.js:58:5
18:27:16     INFO -      co@SimpleTest/SpawnTask.js:54:10
18:27:16     INFO -      setTimeout handler*SimpleTest_setTimeoutShim@SimpleTest/SimpleTest.js:676:12
18:27:16     INFO -      add_task@SimpleTest/SpawnTask.js:269:7
18:27:16     INFO -      runTest@toolkit/components/alerts/test/test_principal.html:113:3
18:27:16     INFO -      @toolkit/components/alerts/test/test_principal.html:119:1
18:27:16     INFO -  997 INFO SpawnTask.js | Leaving test testNodePrincipal

18:22:16     INFO -  1113 INFO SpawnTask.js | Entering test test_buttons_unsupported
18:22:16     INFO -  1114 INFO Extension loaded
18:22:16     INFO -  1115 INFO TEST-PASS | toolkit/components/extensions/test/mochitest/test_ext_notifications.html | notifications.create with buttons option threw an expected exception
18:22:16     INFO -  1116 INFO TEST-PASS | toolkit/components/extensions/test/mochitest/test_ext_notifications.html | buttons-unsupported
18:22:16     INFO -  1117 INFO TEST-PASS | toolkit/components/extensions/test/mochitest/test_ext_notifications.html | test result correct
18:22:16     INFO -  1118 INFO SpawnTask.js | Leaving test test_buttons_unsupported
18:22:16     INFO -  Buffered messages finished
18:22:16    ERROR -  1119 INFO TEST-UNEXPECTED-FAIL | toolkit/components/extensions/test/mochitest/test_ext_notifications.html | message queue is empty - got "[\"closed\"]", expected "[]"
...
18:22:16    ERROR -  1121 INFO TEST-UNEXPECTED-FAIL | toolkit/components/extensions/test/mochitest/test_ext_notifications.html | message queue is empty - Result logged after SimpleTest.finish()

(from the same failing jobs).

Also, interesting to note that all of these ran successfully one time out of ten in the treeherder link above...

Comment 2

[Matthew N. [:MattN]]

(In reply to Dustin J. Mitchell [:dustin] from comment #0)
> Are notifications different on Windows 10 and Windows 7?

No, they should both be XUL notifications, meaning no OS integration.

Comment 3

[Matthew N. [:MattN]]

Btw. I started updating my Win10 environment on the weekend but ran into some hurdles so I wasn't able to run the test on Win10 yet.

Comment 4

[Dustin J. Mitchell [:dustin] (he/him)]

It's not clear this is still going on, so removing the ni.  I may be back once we've re-evaluated what's working and what's not on win10.

Comment 5

[Dustin J. Mitchell [:dustin] (he/him)]

Rob, is this still useful?

Comment 6

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

here's a test run:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=b587c6fd0e17272f2347acbef7587701461a209c&exclusion_profile=false&group_state=expanded

Comment 7

[Dustin J. Mitchell [:dustin] (he/him)]

It looks like that try rev never actually got pushed.  I think enough has changed in the platform since this was filed that it's likely not valid anymore - and anyway, we never really figured anything out.