| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Add some initial #syz invalid support to syz-cluster. For now, mark all
findings as invalid and don't display that such series have findings on
the web dashboard.
|
| |
|
|
| |
Cc syzkaller-bugs@googlegroups.com in all upstreamed syzbot ci findings.
|
| |
|
|
| |
Give more visibility into what the component is doing and why it fails.
|
| |
|
|
|
|
|
|
|
| |
Currently, the list was both within the Series object and within the
SessionReport object that also encloses Series. And, since only was was
actually filled, we were unable to actually Cc the people from the
series.
Keep only the Cc list in the Series object and adjust the tests.
|
| |
|
|
| |
This allows the dashapi-based sender include them in the email address.
|
| | |
|
| |
|
|
|
| |
We use the archive list to track replies, so it must be included in all
our original emails as well.
|
| |
|
|
|
| |
Add [moderation/CI] prefix for moderation emails.
Add a prefix with the service name for reports.
|
| |
|
|
| |
This will facilitate code reuse.
|
| |
|
|
|
| |
Refactor the configuration to support both SMTP and dashapi-based email
sending functionality.
|
| |
|
|
|
|
| |
Replace an UpdateReport() call with a RecordReply(). This will
eventually allow us to support the email sender implementations for
which we do not immediately know the MessageID of the reported message.
|
| |
|
|
|
|
|
|
| |
Since email-reporter is anyway tied to a specific reporting channel,
let's keep reporter names less generic.
Using "lkml" instead of just "email" will also let us generate proper
links to the email discussions based only on Reporter+MessageID.
|
|
|
Add the high-level logic for the email-reporter component that will
be responsible for sending bug reports and reacting to incoming emails.
|
