Closed Bug 519509 Opened 10 years ago Closed 9 years ago
Intermittent xpcshell test timeout (NOT UNEXPECTED-FAIL) in test
_processasync .js (i .e ., after test _name _scheme .js)
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox3.6-Unittest/1254246969.1254250081.12882.gz&fulltext=1 WINNT 5.2 mozilla-1.9.2 test everythingelse on 2009/09/29 10:56:09 That log shows test_name_scheme.js passing, followed by a timeout. This log from a green run: http://tinderbox.mozilla.org/showlog.cgi?log=Firefox3.6-Unittest/1254237953.1254240053.23108.gz&fulltext=1 suggests that test_processasync is the next test to run.
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox-Unittest/1259047998.1259051462.8032.gz WINNT 5.2 mozilla-central test everythingelse on 2009/11/23 23:33:18
Summary: Intermittent reftest timeout in test_processasync.js → Intermittent xpcshell test timeout in test_processasync.js (i.e., after test_name_scheme.js)
Hm, I really need the test output for this. I'll look into seeing what needs to be done to get xpcshell tests to dump the partial output on timeout.
Assignee: nobody → jwalden+bmo
Component: Networking → httpd.js
Product: Core → Testing
QA Contact: networking → httpd.js
http://tinderbox.mozilla.org/showlog.cgi?log=Thunderbird/1264818193.1264824615.4762.gz WINNT 5.2 comm-central check on 2010/01/29 18:23:13
Maybe we can stop misstarring this?
Summary: Intermittent xpcshell test timeout in test_processasync.js (i.e., after test_name_scheme.js) → Intermittent xpcshell test timeout (NOT UNEXPECTED-FAIL) in test_processasync.js (i.e., after test_name_scheme.js)
(In reply to comment #9) > Maybe we can stop misstarring this? I guess not. Everything in this bug in the past 17 months is actually bug 568663. Resolving this bug since it hasn't been seen since January 2010 (comment 3).
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.