test_longThreads.html, test_threadTimeouts.html fail in debug

RESOLVED WORKSFORME

Status

Testing
Mochitest
RESOLVED WORKSFORME
10 years ago
10 years ago

People

(Reporter: jorendorff, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
These two mochitests are failing for me in clean debug builds on my MacBook.

  dom/src/threads/test/test_longThreads.html
  dom/src/threads/test/test_threadTimeouts.html

The *next* test, which is quite unrelated (jquery stuff), also fails.  I suspect the thread tests are causing that too, but it's just a guess.
(Reporter)

Comment 1

10 years ago
Sometimes after one of these tests fails, options.javascript.gczeal is left at 2 (I confirmed this using gdb).  This causes the browser to go comatose.
I disabled gczeal on the tests tonight so that tracemonkey could land (apparently it was breaking their debug builds too). Maybe this is WFM now?
(Reporter)

Comment 3

10 years ago
Yep!  Thanks.

It seems like we ought to be able to have gczeal tests, but turning it off solves my current problem.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.