The test is waiting to run, but LambdaTest keeps it in “queued” for 2 minutes, then switches it to “cancelled,” and this happens over and over again. Sometimes it takes up to 20 minutes just to run a single test.
What could be the issue?
Hey @Art_K Hope you are doing well,
Thanks for reaching out to us,
We reviewed the test ID you shared and noticed that the framework timeout is currently set to 2 minutes. While the device does get allocated, the test is being cancelled due to this timeout limit.
You can increase the framework timeout to avoid such scenarios(upto 10-15min).
Could you please update the timeout accordingly and share your observations once done?
1 Like
It turned out the issue was too many requests for one device, so the test stayed in the queue and then got cancelled. It was fixed by adding multiple devices. So far, it looks good.
1 Like