Graeme McCutcheon [:graememcc] Reporter
	Description • 12 years ago

Welcome to another entry in my occasional series of failures that I hit locally, but which don't seem to affect our trees.

I've started hitting an almost-constant-but-not-quite failure where the test harness opens the browser window, but then gets stuck in the waitForFocus call at http://hg.mozilla.org/mozilla-central/file/f9c2c266e7aa/testing/mochitest/browser-test.js#l154 and thus never starts running the test(s).

Watching on screen, the window visually appears focused, it looks like waitForFocus somehow never gets the focus event.

To verify I wasn't going mad, and that the test I was working on wasn't faulty, I reduced the test to the simple
  function test() {
    ok(true, "TEST WAS RUN");
  }
but the problem persisted. hg bisect blames bug 756313.

Attached is output from NSPR_LOG_MODULES=focus:5 TEST_PATH=browser/base/content/test/browser_bug808420.js make -C obj mochitest-browser-chrome with a patch applied to add that test, which is the trivial test described above, applied on top of a working directory at http://hg.mozilla.org/mozilla-central/rev/00c925c90f86.

	Graeme McCutcheon [:graememcc] Reporter
	Comment 1 • 12 years ago

For contrast, here's NSPR_LOG_MODULES=focus:5 TEST_PATH=browser/base/content/test/browser_bug808420.js make -C obj mochitest-browser-chrome with my trivial test patch applied on top of http://hg.mozilla.org/mozilla-central/rev/556b9cfb269f (the last known good).

	Neil Deakin
	Comment 2 • 12 years ago

What Linux are you using, and which window manager?

	Graeme McCutcheon [:graememcc] Reporter
	Comment 3 • 12 years ago

(In reply to Neil Deakin from comment #2)
> What Linux are you using, and which window manager?
Stock Ubuntu 12.04, so compiz/unity

	Dão Gottwald [:dao]
	Comment 4 • 12 years ago

I'm afraid this sounds like bug 521233.