syz - Unnamed repository; edit this file 'description' to name the repository.

	Commit message (Collapse)	Author	Age	Files	Lines
*	all: use any instead of interface{}	Dmitry Vyukov	2025-12-22	1	-2/+2
\| \| \| \|	Any is the preferred over interface{} now in Go.
*	syz-cluster: ask to leave a credit tag	Aleksandr Nogikh	2025-07-23	1	-0/+2
\| \| \| \| \|	Update the email template to include a suggestion to add a Tested-By tag to the affected series.
*	syz-cluster: configure a Cc list for reported bugs	Aleksandr Nogikh	2025-07-23	1	-1/+3
\| \| \| \|	Cc syzkaller-bugs@googlegroups.com in all upstreamed syzbot ci findings.
*	syz-cluster: generate web dashboard URLs for reports	Aleksandr Nogikh	2025-07-14	2	-0/+28
\| \| \| \| \|	Take web dashboard URL from the config and use it to generate links for logs, reproducers, etc.
*	syz-cluster: support dashapi sender	Aleksandr Nogikh	2025-07-08	1	-2/+68
\| \| \| \| \|	Refactor the configuration to support both SMTP and dashapi-based email sending functionality.
*	syz-cluster: make the displayed title configurable	Aleksandr Nogikh	2025-07-08	1	-0/+3
\|
*	syz-cluster/email-reporter: poll an LKML archive for replies	Aleksandr Nogikh	2025-05-13	1	-0/+2
\| \| \| \| \| \| \| \| \| \|	Add the functionality to poll the specified LKML git archive for the new user replies under the bot's messages. Check out the repository and pull it once in the specified time period. Keep track of the latest processed commit hash. Track the original report ID via In-Reply-To references.
*	syz-cluster: add email-reporter component	Aleksandr Nogikh	2025-05-09	1	-1/+4
\| \| \| \| \|	Add the high-level logic for the email-reporter component that will be responsible for sending bug reports and reacting to incoming emails.
*	syz-cluster: extend EmailConfig	Aleksandr Nogikh	2025-05-09	1	-0/+56
\| \| \| \| \|	Move the configuration from pkg/report to pkg/app and extend it with more information.
*	syz-cluster: separate global env from global config	Aleksandr Nogikh	2025-04-30	1	-0/+61
\| \| \| \| \| \| \| \| \|	Environment variables are convenient for storing values like DB or GCS bucket names, but structured formats are more convenient for the actual service configuration. Separate global-config from global-config-env and add the functionality that queries and parses the config options.
*	syz-cluster: use GCS as blob storage	Aleksandr Nogikh	2025-02-04	1	-12/+7
\| \| \| \| \| \| \|	We already use a GCS emulator for the dev environment, use a separate bucket for blobs. Keep using the local storage driver for unit tests.
*	syz-cluster: initial code	Aleksandr Nogikh	2025-01-22	2	-0/+96
	The basic code of a K8S-based cluster that: * Aggregates new LKML patch series. * Determines the kernel trees to apply them to. * Builds the basic and the patched kernel. * Displays the results on a web dashboard. This is a very rudimentary version with a lot of TODOs that provides a skeleton for further work. The project makes use of Argo workflows and Spanner DB. Bootstrap is used for the web interface. Overall structure: * syz-cluster/dashboard: a web dashboard listing patch series and their test results. * syz-cluster/series-tracker: polls Lore archives and submits the new patch series to the DB. * syz-cluster/controller: schedules workflows and provides API for them. * syz-cluster/kernel-disk: a cron job that keeps a kernel checkout up to date. * syz-cluster/workflow/: workflow steps. For the DB structure see syz-cluster/pkg/db/migrations/.