mochitest-browser-chrome: intermittent "browser_dataman_basics.js | Test timed out", after "ASSERTION: U+0080/U+0100 - U+FFFF data lost"

NEW
Unassigned

Status

--
major
8 years ago
7 years ago

People

(Reporter: sgautherie, Unassigned)

Tracking

(Blocks: 1 bug, {assertion})

Trunk
x86
Windows Server 2003
assertion
Dependency tree / graph

Firefox Tracking Flags

(blocking-seamonkey2.1 -)

Details

(URL)

(Reporter)

Description

8 years ago
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1297425770.1297431305.19136.gz&fulltext=1
WINNT 5.2 comm-central-trunk debug test mochitest-other on 2011/02/11 04:02:50
{
...
TEST-PASS | chrome://mochitests/content/browser/suite/common/dataman/tests/browser_dataman_basics.js | Successfully switched to preferences panel for IDN tests
###!!! ASSERTION: U+0080/U+0100 - U+FFFF data lost: 'legalRange', file e:/builds/slave/comm-cen-trunk-w32-dbg/build/mozilla/js/src/xpconnect/src/xpcconvert.cpp, line 847
...
TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/suite/common/dataman/tests/browser_dataman_basics.js | Test timed out
INFO TEST-END | chrome://mochitests/content/browser/suite/common/dataman/tests/browser_dataman_basics.js | finished in 34741ms
}


Fwiw, this test passes cleanly on my Windows 2000 with an opt build.

Comment 1

8 years ago
I don't think we can block a release on a failing test, but it would be good to get it fixed.
blocking-seamonkey2.1: ? → -

Comment 2

7 years ago
Serge. Do you still see this?
(Reporter)

Comment 3

7 years ago
From recent tests "monitoring", I would assume the timeout part is now WorksForMe.

***

http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1332038829.1332044962.8931.gz&fulltext=1
WINNT 5.2 comm-central-trunk debug test mochitest-other on 2012/03/17 19:47:09

Bug 644753 turned the assertion into a warning, and there are other messages:
{
TEST-START | chrome://mochitests/content/browser/suite/common/dataman/tests/browser_dataman_basics.js
WARNING: malformed uri: file e:/builds/slave/comm-cen-trunk-w32-dbg/build/mozilla/netwerk/base/src/nsURLParsers.cpp, line 158

TEST-INFO | chrome://mochitests/content/browser/suite/common/dataman/tests/browser_dataman_basics.js | run test #5 of 10 (test_permissions_panel)
*** Failed to get string perm.test.label in bundle: chrome://communicator/locale/dataman/dataman.properties

TEST-INFO | chrome://mochitests/content/browser/suite/common/dataman/tests/browser_dataman_basics.js | run test #9 of 10 (test_idn)
WARNING: jschar out of char range; high bits of data lost: 0x3c0: file e:/builds/slave/comm-cen-trunk-w32-dbg/build/mozilla/js/xpconnect/src/XPCConvert.cpp, line 385
}

The test 5 output is expected: see bug 600229 comment 2.

I don't know much about the two warnings.
Maybe they are related to each other? Maybe not.
Should be worth to check, to document or fix.
(See bug 719127 for a possible hint, though the case may not be similar :-|)
Depends on: 644753
You need to log in before you can comment on or make changes to this bug.