Closed
Bug 583030
Opened 14 years ago
Closed 14 years ago
Could not find element in testPreferredLanguage.js
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: aaronmt, Assigned: aaronmt)
References
()
Details
(Whiteboard: [mozmill-test-failure])
MODULE: firefox/Preferences/ TEST: testPreferredLanguage.js FAIL: could not find element Link: Accedi BRANCH: 1.9.1 ERROR - Test Failure: {u'exception': {u'message': u'could not find element Link: Accedi'} : 67 http://hg.mozilla.org/qa/mozmill-tests/file/4e75e1a2e03a/firefox/testPreferences/testPreferredLanguage.js#l67
Comment 1•14 years ago
|
||
Which OS is affected? Only OS X?
Updated•14 years ago
|
Summary: [mozmill] Could not find element in testPreferredLanguage.js → Could not find element in testPreferredLanguage.js
Assignee | ||
Comment 2•14 years ago
|
||
Linux/OS X according to the result server. I was finally able to reproduce this today (just once) in a test-run of this test. I'm wondering if we can take this offline, but how we would switch languages
Comment 3•14 years ago
|
||
We would have to check the accept language header of the http request. Not sure if we can do that with Javascript inside a normal web page. Please also take bug 559836 into account.
OS: Mac OS X → All
Hardware: x86 → All
Comment 4•14 years ago
|
||
Is this still valid? Haven't seen it for a while.
Assignee | ||
Comment 5•14 years ago
|
||
(In reply to comment #4) > Is this still valid? Haven't seen it for a while. Yes still occurs on 1.9.1 and 1.9.2. Just did two runs and happened on the first run for each older branch.
Assignee | ||
Comment 6•14 years ago
|
||
Not seeing this anymore
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Comment 7•14 years ago
|
||
Move of Mozmill Test related project bugs to newly created components. You can filter out those emails by using "Mozmill-Tests-to-MozillaQA" as criteria.
Product: Testing → Mozilla QA
Version: 1.9.1 Branch → unspecified
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
•