Closed jeffbaxter17 closed 3 years ago
sushobhit-lt
commented
3 years ago hey @jeffbaxter17 , I found reason probably due to the maxInstances key, it should be less than or equal to the number of parallel sessions you have.
maxInstances <= concurrency (lambdatest parallel session)
Try to update your conf file,
exports.config = {
...
exclude: [],
maxInstances: 1,
...
}
jeffbaxter17
commented
3 years ago That change doesn't appear to send results in the queue. It instead just creates a new session each time, which takes much longer to run.
On Wed, Nov 4, 2020 at 12:57 PM sushobhit-lt notifications@github.com wrote:
hey @jeffbaxter17 https://github.com/jeffbaxter17 , I found reason probably due to the maxInstances key, it should be less than or equal to the number of parallel sessions you have.
maxInstances <= concurrency (lambdatest parallel session)
Try to update your conf file,
exports.config = {
... exclude: [], maxInstances: 1, ...
}
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/LambdaTest/webdriverio-selenium-sample/issues/11#issuecomment-721883814, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMTZKI5ZFRYBIHGTVDHQRKDSOGIXNANCNFSM4THVPMKA .
sushobhit-lt
commented
3 years ago yes, It will not add tests in lambda queue, rather than webdriverio manages own queue and create new test once previous one executed.
It will not take longer to run as its same either we queue on Lambda side or wdio manages the same.
jeffbaxter17
commented
3 years ago I think there's some confusion somewhere. Let me explain.
Previously when testing - each browser would be its own test and sit in the queue. The script would parse each browser and capabilities, then send this to LambdaTest.
Currently with the suggested fix, when testing against multiple browsers - each browser is not in the queue. Instead, it doesn't fire until the first one starts and stops for each browser that's listed. This seems to defeat the purpose of the queue. It appears from my recent tests that this increases the times for the scripts to finish.
I have saved previous tests and stack traces if this helps with any clarification. They're probably noted in previous tickets as well.
When I have more than one test, the tests that are in the queue do not run and sometimes double after longs periods of waiting. The problem seems to be the amount of time it waits after the test completes. You can see in the stack trace below that the connection does retry and reconnect, but the connection waits 2-5 minutes after the first test completes to move onto the test case.
Here's my conf file: