Closed Bug 782720 Opened 11 years ago Closed 7 years ago

[B2G] test_MochiKit-DOM-Safari.html takes longer than 330s and times out

Categories

(Firefox OS Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jgriffin, Unassigned)

References

()

Details

On B2G CI, the test /tests/MochiKit-1.4.2/tests/test_MochiKit-DOM-Safari.html is taking longer than 330s and is timing out the entire test run.  So, I am disabling it.

This is a recent change; prior to http://github.com/mozilla/mozilla-central/commit/45b1a9246ea82900580f7df3d85cb6fd63e6aa6f this test took ~145s and so didn't time out.  On my own, much faster machine, the test now takes ~200s.

There are no test errors or errors in the logcat when the test is run; it's just much slower than it previously was.

Full log:  http://brasstacks.mozilla.com/autologserver/showlog?file=b3497784-e62e-11e1-9090-22000af4858b.txt.gz
That file can't be found anymore in the b2g.json file, so I'm marking this as wfm.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Uh, never mind, the whole /tests/MochiKit-1.4.2/tests/ directory isn't being run at all.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Ok, this test is running in 44768ms on my emulator. I guess on the b2g boards, it would still take too long.

The test can't really be split, but if the patch for bug 861850 goes in, then we could add a few ok(true) in there to keep the test running longer.

The rest of the /tests/MochiKit-1.4.2/tests/ directory is passing and the other tests are running faster, btw.
Status: REOPENED → RESOLVED
Closed: 10 years ago7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.