Fuzzing in CI: nightly runs per target, crash regressions kept as tests #1247
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sky_line/Slipstream#1247
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #1243.
Scope. The harnesses and runner exist on branch
fuzzing(indra/fuzz,scripts/fuzz/run.sh, presetlinux-fuzz). This ticket makes them continuous.linux-fuzz, buildfuzz_all(cache the build dir; a full clang + ASan build of the libraries is slow, so incremental), runscripts/fuzz/run.sh all 120(2 minutes per target, about 40 minutes total; make the budget a workflow input), uploadfuzz-work/*/crashes/as artifacts on failure, restore and save the grown corpora between runs (cache keyed per target) andrun.sh mergeweekly to keep them small.fuzzwith the target, the sanitizer stack and the artifact path; the workflow never auto-closes.indra/fuzz/corpus/<name>/crash-*and a replay test in the default suite: build each harness a second time without libFuzzer (a tiny standalone driverStandaloneFuzzTargetMain.cppthat callsLLVMFuzzerTestOneInputfor each file argument) under the normal GCC build asfuzz_replay_<name>, registered withsl_add_unit_testunder labelfast(the seed corpora are tiny, so seconds). Under GCC without sanitizers a replay will only catch crashes andLL_ERRS; the same replay under the sanitizer CI build (next ticket) catches memory errors.run.sh check(one pass over seeds with the libFuzzer binaries) as a post-merge job on the sanitizer-capable CI box.scripts/checkmodule that fails when a parser listed inindra/fuzz/README.mdloses its harness, and README "not covered" items (SLBridge, weather tag, mesh header, glTF asset loader, DXT) turn into tickets as their refactors land.Acceptance criteria.
LLSDBinaryParser) is found by the nightly run within its budget and produces the artifact and ticket.fastunit test in the default build; the added replay time is under 1 s.indra/fuzz/README.mddocuments the CI schedule and the "add a regression" flow (already written for the manual case).Effort. 2 to 3 days for the workflow, caches and replay driver. Prerequisite: the first main-session build of
fuzz_all(the harnesses on the branch were written without compiling; expect a round of link fixes, e.g. llprimitive's link closure forfuzz_mesh_*andfuzz_gltf_material).