878769 - TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/debugger/test/browser_dbg_leaktest.js

Status: RESOLVED INCOMPLETE

(DevTools :: Debugger, defect)

Description

[[e-mail]]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130513 Firefox/17.0 (Nightly/Aurora)
Build ID: 20130510090027

Steps to reproduce:

Executed mochitests.


Actual results:

TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/debugger/test/browser_dbg_leaktest.js | uncaught      exception - TypeError: gDebuggee.firstCall is not a function at chrome://mochitests/content/browser/browser/devtools/debugger/     test/browser_dbg_leaktest.js:36 


Expected results:

test should pass

Comment 1

[[e-mail]]

I forgot to attach the rest of stdout:

TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/devtools/debugger/test/browser_dbg_reload-same-script.js |     uncaught exception - ReferenceError: executeSoon is not defined at chrome://mochitests/content/browser/browser/devtools/           debugger/test/browser_dbg_leaktest.js:43

Comment 2

[Panos Astithas (he/him) [:past] (please ni?)]

There is no longer a browser_dbg_leaktest.js test file in the tree. Are you running from the mozila-esr17 branch? I don't see any failures for that test in our build infrastructure, so I'm wondering if you have any local modifications.

In any case I don't think spending any time on this is worth it.

Comment 3

[:Gijs (he/him)]

I've already asked you before (bug 878784 comment 1, bug 878777 comment 1) to add more information before you report test failures. I'm closing all of these as incomplete. If/when you provide some more information on how to reproduce these, they can be reopened.