test-run: show luatest stderr on startup failure#460
Merged
sergepetrenko merged 1 commit intoMay 26, 2026
Conversation
If luatest fails to start (e.g., due to a Lua error in one of the loaded modules), test-run only shows the exit code without the actual error message. Capture stderr from the subprocess and include it in the error message so the cause of the failure is visible right away.
|
coverage: 62.529% (-0.04%) from 62.569% — Godrik0:Godrik0/test-run-capture-stderr into tarantool:master |
Totktonada
approved these changes
May 21, 2026
Contributor
Nope, this is not intentional. Nice to see it fixed. |
ImeevMA
approved these changes
May 25, 2026
Contributor
ImeevMA
left a comment
ImeevMA
left a comment
There was a problem hiding this comment.
Thanks for the patch! It seems very useful!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If luatest fails to start (e.g., due to a Lua error in one of the loaded modules), test-run only shows the exit code without the actual error message. Capture stderr from the subprocess and include it in the error message so the cause of the failure is visible right away.
This may result in verbose error output in some cases. Let me know if the original behavior of discarding stderr was intentional - I found it very inconvenient to debug without seeing the actual error message.