Some time during test_click.py (I'll try to narrow it down), a "Blocked add-on" pop-up comes up and remains in foreground for the remainder of the test run.

I don't see any associated test failures, but this seems like it could be problematic for some tests.

I see this running marionette-tests locally, on the x86-7.0 android emulator with:

./mach marionette-test --app=fennec --disable-e10s --device=127.0.0.1:2828

I also wanted to file that bug earlier today when I run all the Mn tests but finally missed it. So thanks for filing it Geoff!

The problematic test is:

https://searchfox.org/mozilla-central/rev/8e8ccec700159dc4efe061cfec2af10b21a8e62a/testing/marionette/harness/marionette_harness/tests/unit/test_click.py#404-409

But in the finally block the notification should be closed. As it looks like something doesn't work.

Maybe the click is not successful:

https://searchfox.org/mozilla-central/rev/8e8ccec700159dc4efe061cfec2af10b21a8e62a/testing/marionette/harness/marionette_harness/tests/unit/test_click.py#374

So it could be a regression from bug 1487065.

Looking at an example:

https://treeherder.mozilla.org/logviewer.html#?job_id=228733363&repo=try

has the associated logcat:

https://taskcluster-artifacts.net/SZ72m7fRS4CmzQWYFNPsGA/0/public/test_info//logcat-emulator-5554.log

which has, at around the time of this test:

02-15 21:14:00.518 2393 2410 I Gecko : 1550265240518 Marionette DEBUG [16] Canceled page load listener because no navigation has been detected
02-15 21:14:00.519 2393 2410 I Gecko : 1550265240519 Marionette DEBUG 219 <- [1,7,null,{"value":null}]
02-15 21:14:00.522 2393 2410 I Gecko : 1550265240522 Marionette DEBUG 219 -> [0,8,"WebDriver:GetCurrentURL",{}]
02-15 21:14:00.523 2393 2410 I Gecko : 1550265240523 Marionette DEBUG 219 <- [1,8,null,{"value":"http://172.17.0.23:33939/clicks.html"}]
02-15 21:14:00.525 2393 2410 I Gecko : 1550265240525 Marionette DEBUG 219 -> [0,9,"Marionette:GetContext",{}]
02-15 21:14:00.525 2393 2410 I Gecko : 1550265240525 Marionette DEBUG 219 <- [1,9,null,{"value":"content"}]
02-15 21:14:00.532 2393 2410 I Gecko : 1550265240532 Marionette DEBUG 219 -> [0,10,"Marionette:SetContext",{"value":"chrome"}]
02-15 21:14:00.532 2393 2410 I Gecko : 1550265240532 Marionette DEBUG 219 <- [1,10,null,{"value":null}]
02-15 21:14:00.534 2393 2410 I Gecko : 1550265240534 Marionette DEBUG 219 -> [0,11,"WebDriver:FindElement",{"using":"css selector","value":"#notification-popup popupnotification .popup-notification-closebutton"}]
02-15 21:14:00.536 2393 2410 I Gecko : 1550265240536 Marionette DEBUG 219 <- [1,11,{"error":"no such element","message":"Unable to locate element: #notification-popup popupnotification .popup-notificati ... entError@chrome://marionette/content/error.js:389:5\nelement.find/</<@chrome://marionette/content/element.js:339:16\n"},null]
02-15 21:14:00.538 2393 2410 I Gecko : 1550265240538 Marionette DEBUG 219 -> [0,12,"Marionette:SetContext",{"value":"content"}]
02-15 21:14:00.538 2393 2410 I Gecko : 1550265240538 Marionette DEBUG 219 <- [1,12,null,{"value":null}]
02-15 21:14:00.540 2393 2410 I Gecko : 1550265240540 Marionette DEBUG 219 -> [0,13,"WebDriver:DeleteSession",{}]
02-15 21:14:00.542 2393 2410 I Gecko : 1550265240542 Marionette DEBUG 219 <- [1,13,null,{"value":null}]
02-15 21:14:00.545 2393 2410 I Gecko : 1550265240544 Marionette DEBUG Closed connection 219

First, this is not a regression from bug 1487065 which landed recently. It exists for a while and should also occur on the ARM emulator. Reason is that on Android it's not a notification but some kind of alert, which I cannot seem to correctly handle.

James, do you know how the "Blocked Addon" popup/alert/whatever is implemented for Fennec?

(In reply to Henrik Skupin (:whimboo) [⌚️UTC+1] from comment #3)

First, this is not a regression from bug 1487065 which landed recently. It exists for a while and should also occur on the ARM emulator. Reason is that on Android it's not a notification but some kind of alert, which I cannot seem to correctly handle.

James, do you know how the "Blocked Addon" popup/alert/whatever is implemented for Fennec?

Not familiar with this code, but it looks like it gets handled here: https://searchfox.org/mozilla-central/rev/4587d146681b16ff9878a6fdcba53b04f76abe1d/mobile/android/chrome/content/browser.js#5200

Thanks James! I didn't know that there is a custom implementation for prompts in Fennec. That is indeed the reason why we fail here in closing it, even with an updated test for handling alerts. Support for that would depend on a fix for bug 1325738.

Geoff, if you think it would block us in some way then we should simply skip this test for mobile.

I don't know that this issue is causing any actual trouble for the tests, so let's not skip.

This is Fennec, which isn't supported anymore.