Test progress logs not complete when a test times out

NEW

Status

Webtools Graveyard
Tinderbox3
9 years ago
3 years ago

People

(Reporter: mayhemer, Assigned: John Keiser (jkeiser))

Tracking

Details

(Reporter)

Description

9 years ago
I landed a patch where a test had a failure and stopped executing, leaving SimpleTest in waitForExplicitFinish state. That obviously caused timeout. Problem was that look into the logs from all unit test machines gave me a different picture what was the test that timed out.

Please see few logs that should fail in test_offlineMode.html but each show something totally different, all of them are truncated, not complete:

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1233155484.1233158866.4560.gz#err4
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1233155484.1233162469.11629.gz
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1233160757.1233162526.11709.gz
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1233155484.1233160570.8085.gz
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1233160757.1233163165.14184.gz#err4

This complicates analyzes of the failure.
(Reporter)

Comment 1

9 years ago
Any progress on this? I am in the same situation now...
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.