This repository was archived by the owner on Mar 24, 2026. It is now read-only.
Add flag to suppress most stuff written to stdout and stderr#2594
Merged
NateBrady23 merged 1 commit intoTechEmpower:masterfrom Mar 20, 2017
Merged
Add flag to suppress most stuff written to stdout and stderr#2594NateBrady23 merged 1 commit intoTechEmpower:masterfrom
NateBrady23 merged 1 commit intoTechEmpower:masterfrom
Conversation
This is designed for use with continuous benchmarking. Currently, we run continuous benchmarking as an upstart script. By default it puts everything sent to stdout into a file like /var/log/upstart/tfb.log. This log file is absolutely enormous -- it contains everything printed by every framework. It's so big that it fills up the disk of our test environments before a single iteration of the full test suite completes. We work around this by disabling the upstart log completely (declaring "console none" in its config), but that's not ideal because then we have no logs at all. With this change, with quiet mode enabled, we print much, much less to stdout. There should only be a few lines printed per framework. This will let us enable the upstart logs again, which should be useful when trying to answer questions like, "Which framework are we testing right now?"
Member
|
Oh, awesome! |
zloster
pushed a commit
to zloster/FrameworkBenchmarks
that referenced
this pull request
Mar 21, 2017
…ower#2594) This is designed for use with continuous benchmarking. Currently, we run continuous benchmarking as an upstart script. By default it puts everything sent to stdout into a file like /var/log/upstart/tfb.log. This log file is absolutely enormous -- it contains everything printed by every framework. It's so big that it fills up the disk of our test environments before a single iteration of the full test suite completes. We work around this by disabling the upstart log completely (declaring "console none" in its config), but that's not ideal because then we have no logs at all. With this change, with quiet mode enabled, we print much, much less to stdout. There should only be a few lines printed per framework. This will let us enable the upstart logs again, which should be useful when trying to answer questions like, "Which framework are we testing right now?"
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 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.
This is designed for use with continuous benchmarking.
Currently, we run continuous benchmarking as an upstart script. By
default it puts everything sent to stdout into a file like
/var/log/upstart/tfb.log. This log file is absolutely enormous -- it
contains everything printed by every framework. It's so big that it
fills up the disk of our test environments before a single iteration of
the full test suite completes.
We work around this by disabling the upstart log completely (declaring
"console none" in its config), but that's not ideal because then we have
no logs at all.
With this change, with quiet mode enabled, we print much, much less to
stdout. There should only be a few lines printed per framework. This
will let us enable the upstart logs again, which should be useful when
trying to answer questions like, "Which framework are we testing right
now?"