Test failure 'Timeout exceeded for waitForElement ID: url' in /testSecurity/testSafeBrowsingNotificationBar.js

RESOLVED WORKSFORME

Status

Mozilla QA
Mozmill Tests
P2
normal
RESOLVED WORKSFORME
5 years ago
4 years ago

People

(Reporter: whimboo, Assigned: mario garbi)

Tracking

unspecified

Firefox Tracking Flags

(firefox19 affected, firefox23 affected)

Details

(Whiteboard: [mozmill-test-failure] s=130107 u=failure c=security p=1, URL)

(Reporter)

Description

5 years ago
This test failure happened first on Sep 6th and occurs randomly. For now only on Aurora builds.

TimeoutError@resource://mozmill/modules/utils.js:447 waitFor@resource://mozmill/modules/utils.js:485 MozMillController.waitFor@resource://mozmill/modules/controller.js:685 MozMillController.waitForElement@resource://mozmill/modules/controller.js:701 checkNoPhishingButton@resource://mozmill/modules/frame.js -> file:///c:/docume~1/mozilla/locals~1/temp/tmpc5phsm.mozmill-tests/tests/functional/testSecurity/testSafeBrowsingNotificationBar.js:97 testNotificationBar@resource://mozmill/modules/frame.js -> file:///c:/docume~1/mozilla/locals~1/temp/tmpc5phsm.mozmill-tests/tests/functional/testSecurity/testSafeBrowsingNotificationBar.js:36
(Reporter)

Comment 1

5 years ago
Didn't happen anymore since Sep 11th. I will close as WFM but lets reopen once it reappeared.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME

Comment 2

5 years ago
Happened again in 12/22 with the same error message as before, also on Aurora - http://mozmill-ci.blargon7.com/#/functional/report/a11aa7b15f4e571fd6fe21a2dbd49ed6

http://mozmill-ci.blargon7.com/#/functional/failure?branch=All&platform=All&from=2012-09-04&test=%2FtestSecurity%2FtestSafeBrowsingNotificationBar.js&func=testSafeBrowsingNotificationBar.js%3A%3AtestNotificationBar
Status: RESOLVED → REOPENED
status-firefox19: --- → affected
Resolution: WORKSFORME → ---
(Reporter)

Comment 3

5 years ago
Which element is it here we are waiting for?
Status: REOPENED → NEW

Comment 4

5 years ago
(In reply to Henrik Skupin (:whimboo) from comment #3)
> Which element is it here we are waiting for?

The element is the URL field:
http://hg.mozilla.org/qa/mozmill-tests/file/ba1049f1b77f/tests/functional/testSecurity/testSafeBrowsingNotificationBar.js#l98
(Reporter)

Comment 5

5 years ago
No, it's not. The url field is in chrome space but not in content as 'controller.tabs.activeTab' requests. I believe the is text shown in the page which should contain the malicious URL.
(Reporter)

Updated

5 years ago
Whiteboard: [mozmill-test-failure] → [mozmill-test-failure] s=130107 u=failure c=security p=1

Updated

5 years ago
Assignee: nobody → andreea.matei
Status: NEW → ASSIGNED
(Assignee)

Updated

5 years ago
Assignee: andreea.matei → mario.garbi
(Assignee)

Comment 6

5 years ago
 The test is failing while waiting for an element on this report page: 
http://www.google.com/safebrowsing/report_error/?tpl=mozilla&hl=en-US&url=http%3A%2F%2Fwww.mozilla.org%2Ffirefox%2Fits-a-trap.html

 The element in case is the URL input field on the report page and since we get a different message if the page doesn't load it might be a once in a while problem with the page rather that with our test.
(Reporter)

Comment 7

5 years ago
I would love if we could attach screenshots in those cases to the report. I wonder if we really have loaded the right web page in the new tab. We could add a check for that in the meantime.

Otherwise I would say we will wait for the new ESX system to be ready and continue to watch. So far I haven't seen this failure there.

Given that it doesn't happen that frequently we can downgrade to P3.
Priority: P2 → P3
(Assignee)

Comment 8

5 years ago
I wasn't able to reproduce this in the last weeks and it seems we didn't had this error message since 22.12.2012 "Timeout exceeded for waitForElement ID: url". Could we close this with WFM since I cannot reproduce it anymore?
Let's reopen if we see this again.
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago5 years ago
Resolution: --- → WORKSFORME
(Assignee)

Comment 10

5 years ago
Happened again today with Firefox 22.0a2 fr on Windows NT 5.1.2600:
http://mozmill-ci.blargon7.com/#/functional/report/25ad365ca7bcf4905e9b700b4ffef34f

I will look into it as soon as I can, P1 bugs having priority.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
(Assignee)

Comment 11

5 years ago
It would seem it hasn't reproduced since we reopened it in 2013-04-03, closing it for now. Please reopen if it happens again.

http://mozmill-ci.blargon7.com/#/functional/failure?branch=All&platform=All&from=2013-04-01&to=2013-05-21&test=%2FtestSecurity%2FtestSafeBrowsingNotificationBar.js&func=testSafeBrowsingNotificationBar.js%3A%3AtestNotificationBar
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago5 years ago
Resolution: --- → WORKSFORME

Comment 12

4 years ago
Started happening again today on Linux 12.04 x86 with Aurora DE:
http://mozmill-ci.blargon7.com/#/functional/report/f2d3b6136b11cb7b6708636cff249f34
Status: RESOLVED → REOPENED
status-firefox23: --- → affected
Resolution: WORKSFORME → ---
Priority: P3 → P2
(Assignee)

Comment 13

4 years ago
This has only failed once in 16.04.2013 when it was reopened and I cannot reproduce it locally either. Closing it with WFM. Please reopen if it happens again.

Dashboard query between 01/05/2013 and 09/09/2013:
http://mozmill-ci.blargon7.com/#/functional/failure?branch=All&platform=All&from=2013-05-01&to=2013-09-09&test=%2FtestSecurity%2FtestSafeBrowsingNotificationBar.js&func=testSafeBrowsingNotificationBar.js%3A%3AtestNotificationBar
Status: REOPENED → RESOLVED
Last Resolved: 5 years ago4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.