Skip to content
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

Jump to bottom

revive error grouping? #160

Open
derekbruening opened this issue Nov 28, 2014 · 1 comment
Open

revive error grouping? #160

derekbruening opened this issue Nov 28, 2014 · 1 comment
Labels
Component-UI Migrated Priority-Low Type-Feature Usability

Comments

@derekbruening
Copy link
Contributor

From derek.br...@gmail.com on December 10, 2010 17:58:08

PR 486051

When looking at 100k errors in an app, even groups and duplicates didn't
help much as there just too many of them. Also, some groups had too many
errors in them. There was no easy way to tell how many unique errors were
in each group and how much of the total each group constituted. So with
each group, number of unique errors and total number of errors should be
printed. While at it should we print the percentage of total errors a
group constitutes?

Original issue: http://code.google.com/p/drmemory/issues/detail?id=160
@derekbruening
Copy link
Contributor Author

From bruen...@google.com on February 17, 2013 09:31:56

error grouping was something that postprocess.pl used to do. I'm changing this issue to cover potentially adding it back again.

Summary: revive error grouping? (was: print summation of bugs in each group (total and unique))
Labels: Component-UI Usability Priority-Low

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Component-UI Migrated Priority-Low Type-Feature Usability
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@derekbruening