diff options
| author | Dmitry Vyukov <dvyukov@google.com> | 2019-12-11 11:05:32 +0100 |
|---|---|---|
| committer | Dmitry Vyukov <dvyukov@google.com> | 2019-12-11 11:05:32 +0100 |
| commit | 0d368675f84a2d7f3389d4204bdd6a20d1989006 (patch) | |
| tree | e0c3f3a5c8369e973d751009c1ebf1ac3a5ca313 /executor/common_usb.h | |
| parent | 7dbfdaf076af636b5e7f505aca88b7fb97e0de6d (diff) | |
dashboard/app: report newer crashes in the next reporting
We used to report the newest crash long time ago.
Then we switched to preserving the crash across reporting
stages b/c what reaches next stage may be not what was
sent upstream in the previous one.
However, it seems to cause more problems now than it solves.
Crash classification become much better + some backlog
of bugs was clearer, so we don't have that may glued bugs.
However, in some cases we report notoriously old crashes
which is bad. Switch to the newest crash agian.
Let's see how this works now.
Diffstat (limited to 'executor/common_usb.h')
0 files changed, 0 insertions, 0 deletions
