Skip to content

Document the use of counts with eprintln. #263

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.

Sign up for GitHub

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 1 commit into from
Jul 24, 2018
Merged

Document the use of counts with eprintln. #263

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions collector/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -184,8 +184,8 @@ All this is the same as for the `bench_local` subcommand, except that
- **Slowdown**. Depends where the `eprintln!` statements are inserted.
- **Output**. The output of these `eprintln!` statements (and everything else
written to `stderr`) is written to files with an `eprintln` prefix. Those
files can be post-processed in any appropriate fashion; `sort $FILE | uniq
-c` is one possibility.
files can be post-processed in any appropriate fashion;
[`counts`](https://github.com/nnethercote/counts) is one possibility.

## @bors try builds

Expand Down