Try again to fix the Windows debug bloatcycle bustage from bug 540369, by cranking the timeout up to 3540 seconds
authorPhil Ringnalda <philringnalda@gmail.com>
Mon, 25 Jan 2010 21:22:45 -0800
changeset 37501 e436d3c5a4a6db78573ce3d9b59b52ee921d6abf
parent 37500 729b45c96021e66c3e9eddc4b413ea307146e3f0
child 37502 79580340974503c858e85d0c5d3d01ed283d9eda
push id11343
push userphilringnalda@gmail.com
push dateTue, 26 Jan 2010 05:29:27 +0000
treeherdermozilla-central@e436d3c5a4a6 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
bugs540369
milestone1.9.3a1pre
Try again to fix the Windows debug bloatcycle bustage from bug 540369, by cranking the timeout up to 3540 seconds
build/leaktest.py.in
--- a/build/leaktest.py.in
+++ b/build/leaktest.py.in
@@ -75,10 +75,10 @@ if __name__ == '__main__':
     automation.initializeProfile(PROFILE_DIRECTORY)
     browserEnv = automation.environment()
 
     if not "XPCOM_DEBUG_BREAK" in browserEnv:
         browserEnv["XPCOM_DEBUG_BREAK"] = "stack"
     url = "http://localhost:%d/bloatcycle.html" % PORT
     appPath = os.path.join(SCRIPT_DIR, automation.DEFAULT_APP)
     status = automation.runApp(url, browserEnv, appPath, PROFILE_DIRECTORY,
-                               extraArgs, timeout=330.0)
+                               extraArgs, timeout=3540.0)
     sys.exit(status)