aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* pkg/aflow: add package for agentic workflowsDmitry Vyukov2026-01-0916-15/+2032
|
* pkg/osutil: add DiskUsage functionDmitry Vyukov2026-01-097-103/+73
| | | | DiskUsage returns total recursive disk usage of the dir (similar to du -s).
* pkg/report/testdata: regenerateTaras Madan2026-01-0930-32/+15
| | | | Update all the test files. I removed test.Equals() check to do it for all the files at once.
* pkg/report: tune tests generationTaras Madan2026-01-091-1/+7
| | | | | 1. We use empty TITLE and TITLE absence. Let's use TITLE absence by default. 2. FRAME header shouldn't be generated, only updated.
* syz-cluster: poll the media treeAleksandr Nogikh2026-01-091-0/+6
| | | | | | Poll the tree and consider it during patch series triage. Note that the media lists are not monitored as of now, so the tree will only be used when we receive media patches through other mailing lists.
* syz-cluster: increase the number of parallel workflowsAleksandr Nogikh2026-01-091-1/+1
|
* syz-cluster: show series versions in the dashboardPimyn Girgis2026-01-083-1/+27
| | | | | | Display a list of other versions of the same series on the series details page. Fetch all series sharing the same title and render them in a new "Series Versions" table, allowing navigation between different versions of a patch series.
* syz-cluster: add tests for series and patch name filteringPimyn Girgis2026-01-081-0/+88
| | | | Adds unit tests for the series and patch name filtering functionality in the database repository.
* syz-cluster: add filtering by series and patch namePimyn Girgis2026-01-085-12/+45
| | | | | Update SeriesFilter in pkg/db to include PatchName and SeriesName fields, implement the SQL logic to filter by these fields case-insensitively, and expose these filters in the dashboard UI.
* sys/linux: update flags in dev_video4linux.txtJiaming Zhang2026-01-082-6/+53
|
* vm/starnix: update syntax for ffx target listLaura Peskin2026-01-071-2/+1
|
* pkg/coveragedb: add subsystem information about the new filesTaras Madan2026-01-051-1/+19
| | | | | Current logic updates information about the already knows files. Additionally we want to see subsystem information about all the created/added files.
* dashboard/app: fix format in cron.yamlTaras Madan2026-01-051-1/+1
| | | | It fixes the deployment error.
* pkg/coveragedb: fix docsTaras Madan2026-01-051-1/+1
|
* dashboard/app: split handleBug functionDmitry Vyukov2026-01-051-56/+64
| | | | Linter points it become too long.
* dashboard/app: add support for AI workflowsDmitry Vyukov2026-01-0520-5/+1320
| | | | | | | | Support for: - polling for AI jobs - handling completion of AI jobs - submitting job trajectory logs - basic visualization for AI jobs
* pkg/aflow/ai: add packageDmitry Vyukov2026-01-051-0/+12
|
* pkg/aflow/trajectory: add packageDmitry Vyukov2026-01-051-0/+112
|
* .golangci.yml: warn about unused nolint directivesDmitry Vyukov2026-01-021-0/+6
|
* all: remove unused nolint directivesDmitry Vyukov2026-01-0233-58/+13
|
* sys/linux: add reboot/swapon/swapoff/sethostname/setdomainname syscallsDmitry Vyukov2026-01-022-13/+70
|
* sys/linux: fix up dev_video4linux.txtDmitry Vyukov2026-01-021-0/+6
| | | | | | | | | It seems that consts for the file were generated for a single file only, or manually written. I can't find any upstream/linux-next revision where all consts can be regenered. On next-20251111 where we last generated all consts, some of these MALI consts are not present yet. On newer revisions make extract is broken. Add manual defines so that descriptions can be at least re-generated on next-20251111.
* sys/linux: enable some disabled syscalls in snapshot modeDmitry Vyukov2026-01-026-12/+15
| | | | | | Enable some previously disabled syscalls in snapshot mode that look safe for snapshot mode. In snapshot mode we don't rely on the actual networking, and should be able to survive runner process kills, and disk shutdown.
* prog: support snapshot-only callsDmitry Vyukov2026-01-023-20/+27
| | | | Update #5308
* pkg/report: use existing osutil helpers in titleStat codeDmitry Vyukov2026-01-022-34/+8
|
* pkg/manager/html: fix sorting by "Repro Attempts" columnDmitry Vyukov2026-01-021-2/+2
| | | | | Sorting using numSort for column with empty non-number rows does not work. Always print repro attemps, but make 0 inactive (gray).
* dashboard/app: make it possible to test code that uses spannerDmitry Vyukov2025-12-315-0/+96
| | | | | | Start spanner emulator for tests. Create isolated per-test instance+database. Test that DDL migration scripts are work.
* syz-cluster/pkg/db: make it possible to use emulator in dashboard testsDmitry Vyukov2025-12-312-25/+36
|
* syz-cluster: refactor DockerfilesAleksandr Nogikh2025-12-3113-71/+43
| | | | | | | Copy everything into the build context. Add a .dockerignore file to avoid copying the definitely unnecessary files and folders. Check copyrights presence in Dockerfiles.
* dashboard/app: filter out some entries from the error logDmitry Vyukov2025-12-301-20/+19
| | | | | Don't show package update errors, they happen in hundreds every day. Don't show internal datastore bugs (these are not our bugs).
* syz-cluster: add pkg/osutil to Docker containersAleksandr Nogikh2025-12-304-0/+4
| | | | It's become necessary after #6533.
* all: update the demangle packageAleksandr Nogikh2025-12-302-1/+3
| | | | Closes #6524.
* mod: bump google.golang.org/grpc from 1.76.0 to 1.77.0dependabot[bot]2025-12-292-6/+6
| | | | | | | | | | | | | | | Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.76.0 to 1.77.0. - [Release notes](https://github.com/grpc/grpc-go/releases) - [Commits](https://github.com/grpc/grpc-go/compare/v1.76.0...v1.77.0) --- updated-dependencies: - dependency-name: google.golang.org/grpc dependency-version: 1.77.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
* syz-cluster/pkg/db: fix bunch of bugs in emulator managementDmitry Vyukov2025-12-291-56/+55
| | | | | | | | | | | | | | | | | | | There is a bunch of bugs now: 1. The emulator binary is killed when the first test finished, before subsequent tests start. 2. The child emulator binary (the actual emulator "emulator_main") is leaked. These subprocesses are never killed and live past tests. (that's why we get away with the first problem) 3. Errors are not handled well if emulator setup fails. We leave spannerHost empty and subsequent tests ignore the original error (since only the first test executes setupSpannerOnce). 4. NewTransientDB duplicates a bunch of work that needs to happen only once (in particular os.Setenv("SPANNER_EMULATOR_HOST")). Fix all of that. Support spanner emulator distributed as part of google-cloud-sdk while we are here, so that tests can be run locally.
* syz-cluster/pkg/db: don't drop test databasesDmitry Vyukov2025-12-291-17/+2
| | | | | | | | | | | | | | | | | | | | | | This is not necessary, makes things slower, than is not working anyway: === RUN TestSeriesRepositoryUpdate spanner.go:168: failed to drop the test DB: rpc error: code = Canceled desc = context canceled --- PASS: TestSeriesRepositoryUpdate (0.07s) === RUN TestSeriesInsertSession spanner.go:168: failed to drop the test DB: rpc error: code = Canceled desc = context canceled --- PASS: TestSeriesInsertSession (0.11s) === RUN TestQueryWaitingSessions spanner.go:168: failed to drop the test DB: rpc error: code = Canceled desc = context canceled --- PASS: TestQueryWaitingSessions (0.12s) === RUN TestSessionTestRepository spanner.go:168: failed to drop the test DB: rpc error: code = Canceled desc = context canceled --- PASS: TestSessionTestRepository (0.09s) === RUN TestMigrations spanner.go:168: failed to drop the test DB: rpc error: code = Canceled desc = context canceled --- PASS: TestMigrations (0.15s) === RUN TestStatsSQLs spanner.go:168: failed to drop the test DB: rpc error: code = Canceled desc = context canceled
* sys/linux: add v4l2_meta_formatJiaming Zhang2025-12-292-0/+33
|
* pkg/rpcserver: fix race in local server shutdownDmitry Vyukov2025-12-291-10/+21
| | | | | | | | | | | | | | Currently we stop both executor binary and the RPC server concurrently due to use of errgroup.WithContext. As the result, executor may SYZFAIL on the closed network connection before it's killed. This race leads to very high percent (25%) of failed repro attempts for my local syz-manager runs. When we run syz-execprog with Repeat=false, the race triggers frequently. May have something to do with heavily instrumented kernel where some operations may take longer (e.g. killing syz-executor and stopping all of its threads). This should also fix #6091
* pkg/vcs: reduce cyclomatic complexity link funcDmitry Vyukov2025-12-291-47/+63
|
* pkg/vcs: support git@github.com reposDmitry Vyukov2025-12-292-0/+15
|
* pkg/tool: add ServeHTTP functionDmitry Vyukov2025-12-294-30/+23
| | | | Dedup code in syz-ci and syz-hub.
* dashboard/app: wire more admin handlersDmitry Vyukov2025-12-292-31/+6
| | | | | | | Make it possible 3 more admin handlers that look useful for future and safe. Now that we don't deploy the app from local machines, it's problematic to call them without this wiring. Remove one old handler that we don't need anymore.
* mod: bump google.golang.org/api from 0.252.0 to 0.256.0dependabot[bot]2025-12-292-38/+38
| | | | | | | | | | | | | | | | Bumps [google.golang.org/api](https://github.com/googleapis/google-api-go-client) from 0.252.0 to 0.256.0. - [Release notes](https://github.com/googleapis/google-api-go-client/releases) - [Changelog](https://github.com/googleapis/google-api-go-client/blob/main/CHANGES.md) - [Commits](https://github.com/googleapis/google-api-go-client/compare/v0.252.0...v0.256.0) --- updated-dependencies: - dependency-name: google.golang.org/api dependency-version: 0.256.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
* dashboard: extend bug's JSON representationAleksandr Nogikh2025-12-294-20/+73
| | | | Add status, crash, fix, close and commit dates.
* dashboard: factor out uiBugDetails and loadBugDetailsAleksandr Nogikh2025-12-293-121/+138
| | | | | | | Separate the code that loads all details about a particular bug from the code that is only necessary for rendering a bug page on Web UI. These can be used in mass bug exports.
* sys/linux: add Intel TDX descriptionsAlexander Potapenko2025-12-292-0/+103
| | | | | Initial support for Intel TDX as per https://docs.kernel.org/virt/kvm/x86/intel-tdx.html
* sys/linux: update kvm_sev_guest_statusAlexander Potapenko2025-12-291-1/+1
| | | | | | | | | | | According to arch/x86/include/uapi/asm/kvm.h, kvm_sev_guest_status is defined as follows: struct kvm_sev_guest_status { __u32 handle; __u32 policy; __u32 state; };
* pkg/instance: fix 386 repros/jobsDmitry Vyukov2025-12-291-3/+2
| | | | | | | | | | | | All repros and jobs that use syz rerpos are broken for linux/amd64/386 since Mar 2022 with: SYZFAIL: failed to recv rpc aborting RPC server: mismatching manager/executor arches: amd64 vs 386 The problem is that ExecProgInstance.RunSyzProgFile passes sysTarget.Arch (which is VMArch) to syz-execprog, so it expects executor to be amd64. Restore the orignal logic.
* dashboard/app: make static resources work for dev_appserver.pyDmitry Vyukov2025-12-232-0/+7
| | | | | | | | The production app sets CWD to the root of the syzkaller repository, so paths that refer to static resources in app.yaml look like dashboard/app/static/*. However, dev_appserver.py sets CWD to dashboard/app, so these paths do not work. Add soft link dashboard/app/dashboard/app/static that point to dashboard/app/static, so that dashboard/app/static/* paths work from both locations.
* dashboard/app: fix admin checks for dev_appserverDmitry Vyukov2025-12-221-2/+9
| | | | | | Admin checks broke at some point for local app runs (the auth domain is overriden only in tests). Restore proper checking for dev_appserver.
* dashboard/app: improve test names in TestUserAccessLevelDmitry Vyukov2025-12-221-15/+15
| | | | | | The test uses test names with spaces, testing package replaces spaces with _. As the result, it's impossible to search for failed tests, and they all look very similar. Replace space with _, so that it's possible to search for failed tests.
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-11 17:46:10 +0000