Confirmed users
3,816
edits
No edit summary |
No edit summary |
||
| Line 31: | Line 31: | ||
** frequency/consistency - ratio of number of times it was reproduced over number of crashes in batch. (or we might want to replace that with associated bug id and have the ability to file a bug on that crash if need be from there because this measure will always be pretty low given crash URL volume. | ** frequency/consistency - ratio of number of times it was reproduced over number of crashes in batch. (or we might want to replace that with associated bug id and have the ability to file a bug on that crash if need be from there because this measure will always be pretty low given crash URL volume. | ||
** Additional column - we might want to link over to crash stat-s if we can find a reference of that crash in that system. | ** Additional column - we might want to link over to crash stat-s if we can find a reference of that crash in that system. | ||
'''IMPL NOTES:'''crashes from crashtest | |||
* Assertions & Valgrind messages use the same table format: | * Assertions & Valgrind messages use the same table format: | ||
| Line 38: | Line 39: | ||
** os - os it was seen on | ** os - os it was seen on | ||
** frequency/consistency - ratio of runs with this message to total number of runs. We might also want a frequency column to show total number of times we hit this message as well. But I think the consistency is a more important number if you are looking to debug it. | ** frequency/consistency - ratio of runs with this message to total number of runs. We might also want a frequency column to show total number of times we hit this message as well. But I think the consistency is a more important number if you are looking to debug it. | ||
'''IMPL NOTES''': use unittest/assertions document for this and valgrind document for the data | |||
* Tests - show the failing tests that are throwing these messages | * Tests - show the failing tests that are throwing these messages | ||