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

Fail with nonzero exit code if run-operation task encounters an unhandled exception #1377

Closed
drewbanin opened this issue Mar 26, 2019 · 3 comments · Fixed by #1406
Closed
Assignees
Labels
bug Something isn't working

Comments

@drewbanin
Copy link
Contributor

Issue

Issue description

If a run-operation macro fails with an exception (ie. unable to connect to database, invalid SQL, etc), dbt should exit with a nonzero exit code. Moreover, run-operations should generally go through a similar code-path to models, seeds, etc, such that this happens automatically.

Results

The info logs showed that an exception had occurred, but the task exited with exit code = 0

System information

The output of dbt --version:

0.13.0
@drewbanin drewbanin added the bug Something isn't working label Mar 26, 2019
@drewbanin drewbanin added this to the Wilt Chamberlain milestone Mar 26, 2019
@beckjake beckjake self-assigned this Apr 17, 2019
beckjake added a commit that referenced this issue Apr 25, 2019
…turn-codes

Fix run operation return codes (#1377)
@Topsboom
Copy link

Hello, please tell me what the error is or what needs to be done ?
image
image

@Topsboom
Copy link

System task exited with non-zero code.

@jtcohen6
Copy link
Contributor

@Topsboom It's not clear to me what's represented in the screenshots above. What is Arena? Are you calling dbt run-operation commands from there?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants