517130 - Unit test for bug 386495 fails on Fennec

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect)

Description

[John Ford [:jhford] CET/CEST Berlin Time]

Attachment: 386495-fennec

When running the unit test for bug 386495 the browser hangs.  This also causes a lack of output which triggers buildbot's output timeout to kill the test.  This is a fairly common failure.

Comment 1

[cmtalbert]

This issue should block Fennec.  We have two choices:
1. Disable this test for fennec so that it doesn't hamstring other tests
2. Fix this test.

I obviously would lobby for option 2.  

Thoughts?

Comment 2

[John Ford [:jhford] CET/CEST Berlin Time]

I see this hang on at least one n810 every time I look at them.  Maybe we could disable the test until it is known to pass or at least fail in a clean way as it is currently blocking all following unit tests.

Comment 3

[John Ford [:jhford] CET/CEST Berlin Time]

This is still happening and it seems to be killing a lot of unit test runs.

Comment 4

[Martijn Wargers (dead)]

I'm not sure what is exactly wrong with the test itself, it seems to me it should just work fine on Fennec as well.
Does the test cause Fennec to hang or does the test time out?

Comment 5

[John Ford [:jhford] CET/CEST Berlin Time]

I dont know if it is hanging but when i tap the window manager title bar, it reacts as a proper maemo window should and disappears, leaving it's black boarder there.  I would assume that this is just causing the test to block on the popup which means that it doesnt spit out any output for over an hour when buildbot kills it as a timeout.

Comment 6

[BMO Automation]

Closing all opened bug in a graveyard component