-
Notifications
You must be signed in to change notification settings - Fork 6.3k
Assert and stack traces for Bash scripts #12142
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
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
9aad8d6
common.sh: printStackTrace() and assertFail()
cameel b85172b
common.sh: Print the source code from locations indicated in the stac…
cameel 3b1b9a0
common.sh: Adjust formatting in msg_on_error() and add stack trace
cameel 0280c8d
Use fail and assertFail where appropriate in command-line tests
cameel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
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.
Initially I implemented a full assert that you would invoke like this:
assert "[[ $INTERACTIVE == false ]]"It could print the condition if you did not provide a message, which was nice.
The problem is that it required
evalto check the condition and also that quoting was tricky - you had to quote the whole condition with""(otherwise the variables would be evaluated inside the assert rather than in the current function) and then use''over any variable used inside that could evaluate to an empty string.In the end I thought that just a simple
assertFailthat prints a stack trace is enough. It still clearly indicates that the condition you check is an assertion and condition evaluation has no quirks (at least not more than usually in Bash). Also, the condition itself can be seen in the stack trace.