Closed Bug 655885 Opened 14 years ago Closed 14 years ago

'Timeout exceeded for waitForElement ID: getMeOutButton' in testSafeBrowsingWarningPages.js

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: u279076, Assigned: u279076)

References

()

Details

(Whiteboard: [mozmill-test-failure])

Attachments

(1 file, 2 obsolete files)

testSecurity/testSafeBrowsingWarningPage has been failing since May 5th across all platforms for Firefox 6.0a1. Unfortunately, due to bug 650646, we are unable to determine the exact nature of this failure. I'll need to do some investigation before we can clearly state the bug.
Blocks: 655884
I'm not completely sure what the failure point is yet (seems to be near the end of the test -- after clicking the Ignore Warning button on the notification bar). However, I'm noticing a seemingly frequent occurrence of the attack page showing without the warning page displaying (even when the test first starts). I'm going to write a minimized tests which repeatedly tries to load the page.
Attached patch Minimized test (obsolete) — Splinter Review
Henrik, here is a minimized test. To test run: mozmill -b <build> -t <mozmill-tests>/tests/functional/testSecurity/testSafeBrowsingWarningPages_min.js My experience shows that the warning page appears sometimes on first launch but not all the time. Once the warning page appears once, it appears always. You'll have to rerun the test if the first page load is the warning page. It does reproduce fairly easily though.
Assignee: nobody → anthony.s.hughes
Status: NEW → ASSIGNED
Attachment #531226 - Flags: feedback?(hskupin)
Comment on attachment 531226 [details] [diff] [review] Minimized test This failure has been started on May 5th. So I really wonder if you can constantly reproduce it on a Nightly build from May 4th. It kinda smells like a regression or expected change in Firefox.
Attachment #531226 - Flags: feedback?(hskupin)
I'm able to trigger the failure on the 2011-05-04 Nightly build. That said, I can only trigger this failure through Mozmill (ie. the warning page ALWAYS displays if I manually type the URL and try to load the attack page). I'll have to work further to find a regression range.
It's clear now what the failure is since the fix for Mozmill has been landed: Timeout exceeded for waitForElement ID: getMeOutButton Has the button been renamed?
Summary: Unknown Mozmill failure in Security:SafeBrowsingWarningPage → 'Timeout exceeded for waitForElement ID: getMeOutButton' in testSafeBrowsingWarningPages.js
A Pivotal Tracker story has been created for this Bug: https://www.pivotaltracker.com/story/show/13386881
Anthony, can we please make sure to get this issue investigated soon? We have to be sure that this is not a regression in Firefox. Thanks.
Thanks Aaron, this looks like an intentional regression. In other words we will need to update these tests. I've commented on bug 468313 to get clarification from the developers on expected behaviour.
Depends on: 660079
Attached patch Patch v1.0 (obsolete) — Splinter Review
Fixes failures in both Safe Browsing tests by using UtilsAPI.removePermission(). NOTE: This will need to be checked in to both default and mozilla-aurora. NOTE: Check-in of this patch will fix bug 655884 as well.
Attachment #531226 - Attachment is obsolete: true
Attachment #535747 - Flags: review?(gmealer)
Comment on attachment 535747 [details] [diff] [review] Patch v1.0 Per discussion, need to make sure the permission's reset no matter what. Simplest bet is we add it to teardown too.
Attachment #535747 - Flags: review?(gmealer) → review-
Added removePermissions() call to the teardownModule() as well.
Attachment #535747 - Attachment is obsolete: true
Attachment #535751 - Flags: review?(gmealer)
Comment on attachment 535751 [details] [diff] [review] Patch v1.1 [checked-in] Looks good! If you can go ahead and land it, that'd be appreciated. r+
Attachment #535751 - Flags: review?(gmealer) → review+
Attachment #535751 - Attachment description: Patch v1.1 → Patch v1.1 [checked-in]
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: