test/api: silent dump_db() #4276
Merged
Conversation
This file contains 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
When cleaning up api tests, the build job results are dumped from the database to store in build-result.txt and are printed to the runner log at the same time. This makes it very difficult to read results as the database dump prints very long lines that flood the job log. The result isn't really readable (or useful) unless the file is downloaded separately. Silence the `tee` command so that the file is created but no output is printed from the db dump.
jrusz
approved these changes
Jul 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When cleaning up api tests, the build job results are dumped from the database to store in build-result.txt and are printed to the runner log at the same time. This makes it very difficult to read results as the database dump prints very long lines that flood the job log. The result isn't really readable (or useful) unless the file is downloaded separately.
Silence the
teecommand so that the file is created but no output is printed from the db dump.See for example this job log which starts with the last line of the database dump. To see previous lines, you need to switch to the complete raw form.