889817 - Mozmill fails on some locales to correctly set the addonList

Status: RESOLVED DUPLICATE of bug 877100

(Testing Graveyard :: Mozmill, defect)

Description

[Andrei Eftimie]

I first reported this in bug 764640 comment 30
Further investigation tells me its not related at all.

To reproduce the problem, with mozmill 2.0 run the test on Nightly:
> tests/functional/restartTests/testDefaultBookmarks/test1.js

With a en-US build (or a de build) the test will pass.
WIth a jp build the test will not issue the correct PASS statements (they are missing completely).

I've tracked the problem down to this function in mozmill:
https://github.com/mozilla/mozmill/blob/master/mozmill/mozmill/extension/resource/driver/mozmill.js#L89

addons is always null when this fails.

Fails for jp, it, ro.
Works for en-US, de.

Leads me to think it might be some encoding problem, but needs more investigation.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+1]]

What has the default bookmarks tests in common with getting the list of addons? I don't understand this bug. Also keep in mind that we already have bug 877100 for the broken addon retrieval.

Comment 2

[Andrei Eftimie]

Looking into this to assert the relation to bug 877100 
The outcome looks to be the same, lets if the cause is as well

Comment 3

[Andrei Eftimie]

This is indeed related to encoding problems. 
This behaviour has been document last year in bug 793764
Might be need bug 761603 fixed first.

Basically the line:
> addons = converter.ConvertToUnicode(json);
crashes silently, thus addons remains null => this makes the dashboard fail with a JS error

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+1]]

(In reply to Andrei Eftimie from comment #3)
> > addons = converter.ConvertToUnicode(json);
> crashes silently, thus addons remains null => this makes the dashboard fail
> with a JS error

Great! Please tell us the content of json at this stage, which is very important to let me fix the issue.

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Lets follow-up with all information on bug 877100.