When running a script on a remote runner, roughly two kind of errors can occur:
An error occurs reaching the remote runner, meaning that the script could not be scheduled. kan example of this can be network errors reaching our infra.
The script was executed, and it returned an error. In this case the runner returns the k6 error log as a part of the response body.
This PR adds tests asserting that those errors in the response body (2) are sent to Loki regardless of the reported errorCode.
Doesn't actually fix, but related to https://github.com/grafana/synthetic-monitoring-app/issues/835.
When running a script on a remote runner, roughly two kind of errors can occur:
This PR adds tests asserting that those errors in the response body (2) are sent to Loki regardless of the reported
errorCode
.