Closed
Bug 923098
Opened 11 years ago
Closed 11 years ago
Test failure "Current URL should be identical to the target URL" in /testSecurity/testSafeBrowsingWarningPages.js
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect, P2)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mario.garbi, Assigned: mario.garbi)
References
()
Details
(Whiteboard: [mozmill-test-failure][mozmill-2.0] b=trunk r=120950)
Happend on Win 6.2.9200 (x86) with Firefox 27.0a1 'it':
http://mozmill-daily.blargon7.com/#/remote/report/6ec6776efe900da3fd2b64a750c9e17a
Comment 1•11 years ago
|
||
Most likely a problem in the test given that we are much better handling page loads.
Blocks: 744007
Whiteboard: [mozmill-test-failure] → [mozmill-test-failure][mozmill-2.0]
Comment 2•11 years ago
|
||
I tried to reproduce this, but it did't reproduced in 70 runs, I've got only one waitforpageload failure, I will investigate this more tomorrow.
Assignee | ||
Comment 3•11 years ago
|
||
I managed to reproduce it on the win-8-32-3 machine and after manually investigating the issue I noticed that "https://www.mozilla.org/it/firefox/phishing-protection/" does not exists. The page that we are served is a 404 page that has the added /firefox2/ to the path.
This is a remote problem with the mozilla webpage and I'm not sure if we should fix the tests to work around it. I'd say we should get the page fixed instead.
The reason why we don't see this more often is that most of the time we gather path with /firefox2/ on most occasions and only rarely with Mozmill 2.0 we get the correct path. I will log a new Firefox Bug to handle this regression (the page works when opened manually with Chrome).
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → mario.garbi
Status: NEW → ASSIGNED
Comment 4•11 years ago
|
||
(In reply to mario garbi from comment #3)
> "https://www.mozilla.org/it/firefox/phishing-protection/" does not exists.
> The page that we are served is a 404 page that has the added /firefox2/ to
> the path.
This is not only happen for it. Nearly all locales are affected by that.
Assignee | ||
Comment 5•11 years ago
|
||
The locales I have tested (de, fr, ro, ja) redirect us to the en-US page if we try the steps in comment 0 of Bug 924361. The 'it' locale takes us to the "https://www.mozilla.org/it/firefox/phishing-protection/firefox2/" and as such the functionality of the report page is broken for any italian user trying to access it. That is why I was only referring to the 'it' locale, I assume the redirect to the en-US page is intended until we have functional localized pages.
Comment 6•11 years ago
|
||
Francesco, do you know something about that?
Comment 7•11 years ago
|
||
Not really, it's not a part of mozilla.org I usually touch.
it has that page, that's why there's no redirect
http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/it/firefox/phishing-protection/
fr for example doesn't have it
http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/fr/firefox/phishing-protection/
@pascal
Any idea why? I see the last person touching that file was Kohei (now CCed). Is it safe to remove it?
Flags: needinfo?(pascalc)
Comment 8•11 years ago
|
||
/en-US/firefox/phishing-protection/firefox2/ and a redirect from /en-US/firefox/phishing-protection/ have been removed in r116702 as part of Bug 876581. Looks like only the it locale has the localized page. Removed the redirect on trunk in r120950.
OS: Windows 8 → All
Hardware: x86 → All
Whiteboard: [mozmill-test-failure][mozmill-2.0] → [mozmill-test-failure][mozmill-2.0] b=trunk r=120950
Updated•11 years ago
|
Flags: needinfo?(pascalc)
Assignee | ||
Comment 9•11 years ago
|
||
(In reply to Kohei Yoshino [:kohei] from comment #8)
> Looks like only the it locale has the localized page. Removed
> the redirect on trunk in r120950.
Has this revision been landed? I am asking because nothing changed in the page behavior and we are still getting redirected to the error page "https://www.mozilla.org/it/firefox/phishing-protection/firefox2/".
Comment 10•11 years ago
|
||
From the revision number I'd say it landed only on trunk (www-dev.allizom.org), not on stage (www.allizom.org) or production (www.mozilla.org).
No idea who's in charge of moving this over to stage and production (I should have the privileges, not sure though since I never tried).
Flags: needinfo?(kohei.yoshino)
Comment 11•11 years ago
|
||
The patch is not yet landed. :flod, can you try to merge r120950 to stage and production?
Flags: needinfo?(kohei.yoshino)
Comment 12•11 years ago
|
||
Sure, I'll try in a few hours as soon as I get to my computer with the entire repo.
Comment 13•11 years ago
|
||
Ok, tried but I don't have access to those folders.
Comment 14•11 years ago
|
||
Assignee | ||
Comment 15•11 years ago
|
||
The failures stopped with latest Nightly 'it' so this seems to be fixed, thank you guys.
Green runs:
http://mozmill-crowd.blargon7.com/#/remote/report/ec449c026814fd64783d738c02c94ccd
http://mozmill-crowd.blargon7.com/#/remote/report/ec449c026814fd64783d738c02c95936
http://mozmill-crowd.blargon7.com/#/remote/report/ec449c026814fd64783d738c02c96069
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•5 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
•