You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In PR #169, error was added to the possible statuses of the CR. Currently, this state happens only on insufficient number of VUs.
In PR #401, error upon loading output from initializer pod has also been added as error state.
Consider all the cases when the test run should enter that state and adjust the logic accordingly.
Related issue: #75
Review and close it as needs be.
In case of cloud output, failed authentication should cause error state. Right now, error is just logged by the operator while initializer pod exits successfully. K6 resource is stuck in "initialization" and is not being cleaned up.
In PR #169,
error
was added to the possible statuses of the CR. Currently, this state happens only on insufficient number of VUs.In PR #401, error upon loading output from initializer pod has also been added as
error
state.Consider all the cases when the test run should enter that state and adjust the logic accordingly.
Related issue: #75
Review and close it as needs be.
Docs on k6 error codes:
The text was updated successfully, but these errors were encountered: