Documentation
¶
Overview ¶
Command sqlancer-triage classifies SQLancer soak-log output (and the wadjet server logs captured next to it) into genuine oracle violations, wadjet-crash echoes, and ordinary SQL-surface noise. See tools/sqlancer/triage's package doc and tools/sqlancer/README.md's "Triage protocol" for why this exists instead of a grep.
Usage:
sqlancer-triage <file-or-dir>...
Each argument may be a plain-text log, a ".gz" log (transparently decompressed), or a directory (walked recursively for *.log/*.log.gz, skipping "data" and "nats" subdirectories — a soak pair's wadjet data/NATS store dirs, never log output).
Exit status is non-zero if any argument couldn't be classified at all, or if any file was only partially scanned (e.g. a line past this package's line-length cap, or a corrupt gzip stream) — the printed report still runs to completion using whatever was read, but a non-zero exit means its counts are a floor, not a complete answer, and a script driving this command should not treat that report as authoritative.
Source Files