433097 - Error "Cc is not defined" while running test_prompt.html on qm-centos5-03

Status: RESOLVED WORKSFORME

(Toolkit :: Password Manager, defect)

Description

[Daniel Holbert [:dholbert]]

We just hit an apparently sporadic test failure on qm-centos5-03:

*** 47430 ERROR FAIL | Error thrown during test: Cc is not defined | got 0, expected 1 | /tests/toolkit/components/passwordmgr/test/test_prompt.html

The log is:
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1210365780.1210369931.10563.gz

The test itself is:
http://bonsai.mozilla.org//cvsblame.cgi?file=mozilla/toolkit/components/passwordmgr/test/test_prompt.html

Note that the test includes "prompt_common.js" which defines 
   const Cc = Components.classes;

So Cc should be defined.

Comment 1

[Justin Dolske [:Dolske]]

Hmm. Not sure what to do about this, because this shouldn't happen!

One interesting tidbit... The log reports:

*** 47429 INFO Running /tests/toolkit/components/passwordmgr/test/test_prompt.html...
*** 47430 ERROR FAIL | Error thrown during test: Cc is not defined | got 0, expected 1 | /tests/toolkit/components/passwordmgr/test/test_prompt.html

So the exception is being thrown early, or else there would be other output as the individual checks in the test execute. I'd guess this is being thrown in initLogins(), since that's the first run-time use of Cc?

A normal run looks like:

*** 47429 INFO Running /tests/toolkit/components/passwordmgr/test/test_prompt.html...
*** 47430 INFO PASS | Access Ci
*** 47431 INFO PASS | Access Cc
*** 47432 INFO PASS | Access Cc[@mozilla.org/passwordmanager/authpromptfactory;1]

47430/47431 are the ok() checks at the top of prompt_common.js, where Ci and Cc are defined. That output isn't present in the failed log, which would imply that the load of prompt_common.js failed. Not sure what could cause that.

Another interesting note is that there was a failure in this test yesterday, caused by test_prompt.html's subtest 1000 getting an onload for its iframe before we got the authentication prompt the load should have triggered. That could also be a symptom of the failed load?

Comment 2

[Justin Dolske [:Dolske]]

Haven't seen this on any of the tinderboxes since this was filed. Not sure where to even start looking at it since it isn't reproducible now anyway. I guess we'll just assume it was caused and fixed by some other issue, and reopen if it happens again.