-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Print stacktrace on exception in init context or setup/teardown #1971
Conversation
also exit with error code 107 for both cases. fixes #994
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly LGTM, though I'd like to play around with it a bit before it's merged.
Should we try to release this in k6 v0.32.0?
I specifically didn't add it as v0.32.0, because I also wonder, it's pretty small and the worst case is ... somehow it breaks some stacktrace case?!? On the other hand,today is the cut off date so ;) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, and works fine from what I could test.
Agree with Ned that a more complex test is needed. Maybe just replicating the example from #994 with setup()
and teardown()
?
👍 for releasing this in v0.32.0.
Co-authored-by: Ivan Mirić <[email protected]>
also exit with error code 107 for both cases.
fixes #994