Closed Bug 874429 Opened 7 years ago Closed 4 years ago

Intermittent test_form_autocomplete.html | Test timed out | test_form_autocomplete_with_list.html | undefined Checking menu entry #0 - got PASS1, expected bc dæ | undefined Checking menu entry #1 - got final, expected abaæl | Autocomplete popup not...


(Toolkit :: Form Manager, defect)

Not set



Tracking Status
firefox25 --- disabled
firefox26 --- disabled
firefox27 --- disabled
firefox39 --- wontfix
firefox40 --- wontfix
firefox41 --- fixed
firefox-esr24 --- disabled
firefox-esr31 --- wontfix
firefox-esr38 --- wontfix


(Reporter: RyanVM, Assigned: MattN)



(Keywords: intermittent-failure)


(2 files)

Attached image screenshot

Windows XP 32-bit mozilla-inbound debug test mochitest-5 on 2013-05-20 12:34:58 PDT for push 905e081060c5
slave: t-xp32-ix-082

13:50:48     INFO -  175118 ERROR TEST-UNEXPECTED-FAIL | /tests/toolkit/components/satchel/test/test_form_autocomplete.html | Test timed out.
13:50:50     INFO -  175203 ERROR TEST-UNEXPECTED-FAIL | /tests/toolkit/components/satchel/test/test_form_autocomplete_with_list.html | undefined Checking menu entry #0 - got PASS1, expected bc dæ
13:50:50     INFO -  175204 ERROR TEST-UNEXPECTED-FAIL | /tests/toolkit/components/satchel/test/test_form_autocomplete_with_list.html | undefined Checking menu entry #1 - got final, expected abaæ
13:50:50     INFO -  175208 ERROR TEST-UNEXPECTED-FAIL | /tests/toolkit/components/satchel/test/test_form_autocomplete_with_list.html | Autocomplete popup not expected during test 200
13:50:50     INFO -  175210 ERROR TEST-UNEXPECTED-FAIL | /tests/toolkit/components/satchel/test/test_form_autocomplete_with_list.html | Checking form3 input - got d, expected Foo
13:56:17     INFO -  175212 ERROR TEST-UNEXPECTED-FAIL | /tests/toolkit/components/satchel/test/test_form_autocomplete_with_list.html | Test timed out.
Justin, could you please look into this or suggest someone who can?
Flags: needinfo?(dolske)
From a quick skim of 3 recent failures, they all start to timeout here:

05:15:06     INFO -  176231 INFO TEST-PASS | /tests/toolkit/components/satchel/test/test_form_autocomplete.html | Starting test #252
05:15:06     INFO -  176232 INFO TEST-PASS | /tests/toolkit/components/satchel/test/test_form_autocomplete.html | 252 Checking length of expected menu
05:15:06     INFO -  176233 INFO TEST-PASS | /tests/toolkit/components/satchel/test/test_form_autocomplete.html | 252 Checking menu entry #0
05:15:07     INFO -  176234 INFO TEST-PASS | /tests/toolkit/components/satchel/test/test_form_autocomplete.html | Starting test #253
05:15:07     INFO -  176235 INFO TEST-PASS | /tests/toolkit/components/satchel/test/test_form_autocomplete.html | 253 Checking length of expected menu
05:15:07     INFO -  176236 INFO TEST-PASS | /tests/toolkit/components/satchel/test/test_form_autocomplete.html | 253 Checking menu entry #0

...then nothing but a bunch of --DOCSHELL and --DOMWINDOW (GC/CC) until the test finally times out.

It's slightly suspicious that the last modification to this test (bug 875274) was just a couple days after this bug was filed. But it landed _after_ this was filed, so can't directly be responsible. :) Makes me wonder if something landed to prepare the way and made this start to fail, though.

More likely is that test #252 is using a setTimeout() (!!!) to launch test #253, and something now happens after the timeout now to make things go screwy? It's a little weird because 252-->253 is checking to see that nothing happens after typing a space, so in theory the setTimeout isn't really evil here. Unless something now does happen, as so this fails intermittently. The screen shot shows the expected values in the <input>. Beyond that will need some debugging to figure out what the autocomplete stuff is doing.

The Hg history is a little muddy, but afaict this setTimeout was added by Enn in bug 697377 as part of the async form history work. Tag, you're it.
Assignee: nobody → enndeakin
Flags: needinfo?(dolske)
I guess I should also mention that I'm assuming the test_form_autocomplete.html timeout is the important failure, and that the following test_form_autocomplete_with_list.html failure is just because the test ended uncleanly.
Component: Autocomplete → Form Manager
Neil, have you had a chance to look at this yet, by chance? :)
Flags: needinfo?(enndeakin)
I have looked into, but haven't got a failing case with any useful logging yet.
Flags: needinfo?(enndeakin)