parallel(runITsTasks)

// JENKINS-34376 seems to make it hard to detect the aborted builds
} catch (org.jenkinsci.plugins.workflow.steps.FlowInterruptedException e) {
    echo "[FAILURE-002] FlowInterruptedException ${e}"
    // this ambiguous condition means a user probably aborted
    if (e.causes.size() == 0) {
        currentBuild.result = "ABORTED"
    } else {
        currentBuild.result = "FAILURE"
    }
    throw e

parallel(runITsTasks)

// JENKINS-34376 seems to make it hard to detect the aborted builds
} catch (org.jenkinsci.plugins.workflow.steps.FlowInterruptedException e) {
    echo "[FAILURE-002] FlowInterruptedException ${e}"
    // this ambiguous condition means a user probably aborted
    if (e.causes.size() == 0) {
        currentBuild.result = "ABORTED"
    } else {
        currentBuild.result = "FAILURE"
    }
    throw e

# Exceptions - `HTTPException` and `WebSocketException`

These are the exceptions that you can raise to show errors to the client.

When you raise an exception, as would happen with normal Python, the rest of the execution is aborted. This way you can raise these exceptions from anywhere in the code to abort a request and show the error to the client.

You can use:

* `HTTPException`
* `WebSocketException`

        super(message, e);
        this.url = url;
        this.abort = abort;
    }

    public String getUrl() {
        return url;
    }

    public boolean aborted() {
        return abort;
    }

    testIdentifier: TestIdentifier,
    testExecutionResult: TestExecutionResult,
  ) {
    if (!testIdentifier.isContainer) {
      when (testExecutionResult.status!!) {
        TestExecutionResult.Status.ABORTED -> printStatus("-")
        TestExecutionResult.Status.FAILED -> printStatus("F")
        TestExecutionResult.Status.SUCCESSFUL -> printStatus(".")
      }
    }
  }