| zeljkofilipin added a comment. |
Albert Sison (Sauce Labs Help Center)
Feb 3, 1:20 PM PST
Hello,Thanks for writing in to Sauce Labs support. Regarding this specific ”Internal Server Error", this means the VM to run the test started and then become unresponsive. The VM appears to have hit a resource limit and crashed. It’s hard to tell exactly what limit was hit. Later our services tried to restart the VM, but by that point the test was no longer registered as an active job (i.e. it had “gone stale”), and the job failed. This is a type of failure we’ve seen before: where a VM hits a resource limit and crashes. It’s a known problem where we don’t know the exact cause, not enough to prevent it from happening again. In the engineer’s words, it is a “rare but expected scenario”. More information about this error can be found here: https://wiki.saucelabs.com/display/DOCS/Common+Error+Messages#CommonErrorMessages-InternalServerError
As for the "The connection with your VM was lost and your job can't complete." error, if you only get this message rarely and randomly, it is probably a fluke on our end caused by an infrastructure blip as mentioned on our error page: https://wiki.saucelabs.com/display/DOCS/Common+Error+Messages#CommonErrorMessages-TheConnectionwithYourVirtualMachinewasLostandYourJobCan'tComplete
For "The Sauce VMs failed to start the browser or device." error, what percentage of your tests are affected by this specific error? I noticed all the Sauce job URLs provided were testing against Linux/Chrome 48. For diagnostic purposes, can you try testing against a different OS such as Windows 10 or OSX and let us know if you notice any improvements? Thanks for your patience and understanding.
Regards,
Albert
Cc: hashar, zeljkofilipin, thiemowmde, Aklapper, Tobi_WMDE_SW, D3r1ck01, Izno, Wikidata-bugs, aude, Mbch331, greg
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
