Closed
Bug 668876
Opened 15 years ago
Closed 13 years ago
/testPopups/testPopupsBlocked.js fails sometimes in Functional testrun
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: Aleksej, Unassigned)
Details
(Whiteboard: [testday-20110701])
/testPopups/testPopupsBlocked.js testPopUpBlocked fails for me sometimes (probably in less than 50%) when run as part of the “functional” testrun.
http://mozmill-crowd.brasstacks.mozilla.com/#/functional/failure?branch=All&platform=All&from=2011-06-24&to=2011-07-01&test=%2FtestPopups%2FtestPopupsBlocked.js&func=testPopUpBlocked
One of the testrun reports: http://mozmill-crowd.brasstacks.mozilla.com/#/functional/report/3e673a01042add46ed7599eaba63f227
Expression "{"value":"popup-blocked"}" returned null. Anonymous == false
([object XULElement],"{\"value\":\"popup-blocked\"}",10,[object Array])@resource://mozmill/modules/elementslib.js:486 ()@resource://mozmill/modules/elementslib.js:501
* Firefox 7.0a1 (7.0a1, ru, 20110701030757)
* Debian GNU/Linux wheezy/sid (x86_64)
* Mozmill 1.5.4b5 (as a part of mozmill-env)
Comment 1•15 years ago
|
||
We have never seen this issue. Just to ask, Firefox was in the front when that test has been run?
| Reporter | ||
Comment 2•15 years ago
|
||
IIRC, if I understood correctly which testrun it was, yes at least in the last case, and there was no screensaver interfering.
Comment 3•14 years ago
|
||
Aleksej, you have mentioned that it sometimes broke when you run the test as part of the functional test-run. I wonder if it also happens when you run it as a single test.
| Reporter | ||
Comment 4•14 years ago
|
||
Comment 5•14 years ago
|
||
Hm, so even in this case it should be related to another test which gets executed before the failing test. Would you be able to run the same steps as for the search engines failure and try to nail down, which other test is involved here? That would be fantastic!
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 6•13 years ago
|
||
Aleksej, does the problem still persist for you with the latest version of Mozmill and Firefox Nightly?
| Reporter | ||
Comment 7•13 years ago
|
||
I guess it’s too late to think it would; it didn’t happend during the two runs I did yesterday.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Comment 8•13 years ago
|
||
Thanks a lot for the feedback!
Updated•7 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•