It's hard/impossible to know what timed out with this log: http://tinderbox.mozilla.org/showlog.cgi?tree=Firefox-Unittest&errorparser=unittest&logfile=1245698518.1245701368.10344.gz&buildtime=1245698518&buildname=OS%20X%2010.5.2%20mozilla-central%20test%20everythingelse&fulltext=1
It's neither hard nor impossible. Find another test run that passed, find the last test that passed from your timing-out test above in the good log, and then see what the next test run is. buildbot has no idea what the tests are doing internally, so it can't really tell you. If you think the harness should be reporting what test it should be executing before it starts, please reassign appropriately.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WONTFIX
Status: RESOLVED → REOPENED
Component: Release Engineering → Build Config
Product: mozilla.org → Core
QA Contact: release → build-config
Resolution: WONTFIX → ---
Summary: Build timeout with no reason for timeout given → Test harness should report what test it's running at the beginning so that timeout reports are more meaningful
Version: other → Trunk
Component: Build Config → Mochitest
Product: Core → Testing
QA Contact: build-config → mochitest
Do you remember what kind of test this was? Mochitest prints "INFO Running ..." before starting each test. Was this a reftest?
Status: REOPENED → RESOLVED
Last Resolved: 9 years ago → 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.