Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(lambda): handle nonzero codes from workers #2766

Conversation

bernardobridge
Copy link
Contributor

@bernardobridge bernardobridge commented May 20, 2024

Description

Currently errors from workers still make the main CLI process exit with 0. This is inconsistent with Local and Fargate, and can lead to incorrect behaviour in CI and Artillery Cloud (e.g. filtering). Particularly relevant for things like expect.

Note: this API will allow us to define specific exit codes for different types of workerErrors (e.g. TestDataSync), but right now I have just defaulted to 1 for everything. Only in the case of ArtilleryErrors, it will use the exitCode from the CLI in the worker.

Pre-merge checklist

  • Does this require an update to the docs? No
  • Does this require a changelog entry? Yes

@bernardobridge bernardobridge requested a review from a team May 20, 2024 09:36
@bernardobridge bernardobridge force-pushed the bernardobridge/art-1831-handle-non-zero-exit-codes-from-lambda-worker-eg-expect branch from ee181de to b109989 Compare May 20, 2024 09:37
@bernardobridge bernardobridge changed the title fix(lambda): handle cli nonzero codes from workers fix(lambda): handle nonzero codes from workers May 20, 2024
@bernardobridge bernardobridge merged commit c1fd1fe into main May 20, 2024
29 checks passed
@bernardobridge bernardobridge deleted the bernardobridge/art-1831-handle-non-zero-exit-codes-from-lambda-worker-eg-expect branch May 20, 2024 20:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant