-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timed out after 10 seconds for saving storage data #8
Comments
I've just released 1.0.10 to fix this (it should be available soon). You'll need to add the following configuration: <timeOutSeconds>20</timeOutSeconds> |
Thanks for your quick fix. I hope you know that configuration "timeOutSeconds" is already been used for time out the testing page running time. If a huge testing page contains thousands of test case, it will be time out within 20 seconds. After your update, this time out value will be used in two different phase, one is page time out, the other is save storage time out. |
Yes - I'll fix that in the next release. Just did a quick-fix to get past the first issue. |
OK, I've created a new release. The default save timeout is now 15 seconds, but you can change it with: <timeOutSecondsForSave>20</timeOutSecondsForSave> |
Thanks very much, you rocks! |
Dear admin,
We use this plugin to do regular jscover scan in our project. But it has a limitation with 10 seconds to save storage data. I found below code. We have a big project to scan, the result is big. May you give us a configuration or make 30 seconds around?
new WebDriverWait(webClient, 10).until(ExpectedConditions.textToBePresentInElementLocated(By.id("storeDiv"), "Coverage data stored at"));
Thanks,
Chuanyu
The text was updated successfully, but these errors were encountered: