[google/syzkaller] 28a0e9: syz-manager: separate candidate triage jobs in the UI

0 views
Skip to first unread message

Aleksandr Nogikh

unread,
Jun 3, 2026, 8:49:18 AM (6 days ago) Jun 3
to syzk...@googlegroups.com
Branch: refs/heads/gh-readonly-queue/master/pr-7442-13a480e4a3dea8bd1c83796b6552cd77813d46bb
Home: https://github.com/google/syzkaller
Commit: 28a0e909a75bc2255460a4bdba5151efe5a7a2d1
https://github.com/google/syzkaller/commit/28a0e909a75bc2255460a4bdba5151efe5a7a2d1
Author: Aleksandr Nogikh <nog...@google.com>
Date: 2026-06-03 (Wed, 03 Jun 2026)

Changed paths:
M pkg/fuzzer/fuzzer.go
M pkg/fuzzer/job.go
M pkg/fuzzer/stats.go
M pkg/manager/http.go

Log Message:
-----------
syz-manager: separate candidate triage jobs in the UI

Currently, candidate triage jobs are grouped together with regular triage
jobs in the manager's web UI, making it impossible to view them
separately.

Introduce a new JobType enum for fuzzer jobs and assign a dedicated
JobCandidateTriage type to candidate triage jobs. Update the dashboard
links and the HTTP handler in pkg/manager to support filtering and
displaying candidate triage jobs specifically.


Commit: effda7f9de25038cc08e68b6cd8ef1d9b02772aa
https://github.com/google/syzkaller/commit/effda7f9de25038cc08e68b6cd8ef1d9b02772aa
Author: Aleksandr Nogikh <nog...@google.com>
Date: 2026-06-03 (Wed, 03 Jun 2026)

Changed paths:
M pkg/fuzzer/stats.go

Log Message:
-----------
pkg/fuzzer: use JobType constants for UI stat links

Update the links in `pkg/fuzzer/stats.go` to use the `JobType` enum
constants instead of raw string literals. This ensures consistency
with the rest of the job type refactoring and prevents potential typos
if job types are renamed in the future.


Compare: https://github.com/google/syzkaller/compare/28a0e909a75b%5E...effda7f9de25

To unsubscribe from these emails, change your notification settings at https://github.com/google/syzkaller/settings/notifications

Aleksandr Nogikh

unread,
Jun 3, 2026, 9:02:17 AM (6 days ago) Jun 3
to syzk...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages