Saucelabs errors sometimes not reported

[LaurentGoderre]

I discovered this bug because our task is using environment variables that were not set on my local setup. A null value was added to the tags array which created an invalid JSON. Saucelabs instead of returning a 400 or any HTTP error, it returns a 200 but adds a "status": "test error".

This error is not caught and creates a un-ending loop until the timeout is reached.

[Jonahss]

Ooh I like this error report, thanks. Will fix...

[LaurentGoderre]

I did report this to SauceLabs as well so it might get resolved but then again it probably better to fullproof it. There might be other config that creates this problem.

[LaurentGoderre]

Also to clarify my report, the error occurs on the status calls, not the job creation call. SauceLabs thinks it created the job because it returns a job id but it actually didn't.

[Jonahss]

Oh! A job id is returned, but the Job itself never starts at all? ever?

On Mon, Dec 15, 2014 at 6:17 AM, Laurent Goderre [email protected] wrote:

Also to clarify my report, the error occurs on the status calls, not the job creation call. SauceLabs thinks it created the job because it returns a job id but it actually didn't.

— Reply to this email directly or view it on GitHub https://github.com/axemclion/grunt-saucelabs/issues/177#issuecomment-66999514 .

[LaurentGoderre]

The UI doesn't even list the job. They aware of the bug and are working on it on their end but it is possible that other combination could trigger this behavior.

[michaelkantor]

For what its worth, I'm currently seeing something similar:

{
    "completed": false,
    "js tests": [
        {
            "status": "test error",
            "platform": [
                "OSX 10.9",
                "chrome",
                "latest-1"
            ],
            "id": "some-id...",
            "job_id": "job not ready"
        }
    ]
}

No job shows up in the Dashboard.