diff options
| author | Aleksandr Nogikh <nogikh@google.com> | 2022-11-06 19:51:41 +0000 |
|---|---|---|
| committer | Aleksandr Nogikh <wp32pw@gmail.com> | 2022-11-07 11:45:47 +0100 |
| commit | ac259f2d9db8bd79633aee90902c9d865af11a9b (patch) | |
| tree | 43dc7f859a00c62cc5edbb832d881dc97f036994 /executor | |
| parent | da0a628bc7b570a54a849c03919bd53d893b1c17 (diff) | |
dashboard: infer bug info from subject and mailing list
Currently we only determine the bug by looking at the hash encoded after
'+' in syzbot's email address. Users tend to forget to Cc the right
email address while interacting with the bot. Also, it turns out that if
the bug was only sent to Google Groups, any reply to the email thread
does not include the topic starter email address.
Instead of only relying on the right address, try to infer the bug that
was meant by looking more closely at the incoming email.
Parse the mail subject to extract thee title and the sequence number of
the bug.
Extract the mailing list through which the bug was routed to syzbot.
Fetch and filter matching bugs.
If only one matches, handle the command as if it the bug were explicitly
specified.
Diffstat (limited to 'executor')
0 files changed, 0 insertions, 0 deletions