I'll upload a pre-compiled jar with the above patch if necessary. + // we allow the Suite to run 3 times as long as per default (30 min -> 90 min).
+ // SFR, Patch : To get rid of the damn SeleniumCommandTimedOutException a/java/server/src/org/openqa/selenium/server/htmlrunner/HTMLLauncher.java Dont make any changes on the Safe mode start window. Start Firefox in Diagnose Firefox issues using Troubleshoot Mode to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes). diff -git a/java/server/src/org/openqa/selenium/server/htmlrunner/HTMLLauncher.java b/java/server/src/org/openqa/selenium/server/htmlrunner/HTMLLauncher.java That is a problem with an AVG extension (tavgp). I created a small and simple patch for the HTMLLauncher.java to allow 90 minutes instead of the default 30. So choose for yourself which option is better. Patching selenium to run longer than 30 minutes.Rewriting our testsuites and splitting them to run within the 30 minutes window.The -browserTimeout parameter isn't usefull as i haven't found where this parameter is used in the source.Īs we have some testsuites that run longer than 30 minutes we have 2 options to fix this behaviour:.To Reset Firefox do the following: Go to Firefox > Help > Troubleshooting Information. Note: This will cause you to lose any Extensions, Open websites, and some Preferences. These messages are independent to the timeout-value. The Reset Firefox feature can fix many issues by restoring Firefox to its factory default state while saving your essential information. As soon as you specify -timeout (no matter which value), the script timeout appears after several seconds or minutes.
After that, firefox gets killed by selenium with a SeleniumCommandTimedOutException If you don't specify -timeout, firefox runs for exact 30 minutes, without one script timeout.After hours of debugging and testing i noticed some facts: So creating a custom firefox profile template and setting the dom.max_script_run_time and dom.max_chrome_script_run_time will not work here.Īs soon as you specify the -timeout parameter, these two settings are overriden with the value you provide to the parameter. The core of the problem is the fact, that selenium overrides profile settings if you specify the -timeout nnnn parameter. Their main piece of advice was to run their website on IE and not Firefox. One of the offenders of this unresponsive script stuff sent me some help. The javascript used in your application is too fat or buggy, improving your scripts will help.Īs this is no option in a larger company, when you depend on a framework you have no access to, i decided to search for the root cause for myself. Hi - I'll be interested to find out what you learn. Asking the devolopers / mailing list / google usually results in the following answer: I've got these really annoying messages quite a long time now, without a good fix. Although this thread is quite old, the problem still exists with current selenium and firefox builds.
0 kommentar(er)
