sqlancer
Automated testing to find logic and performance bugs in database systems
Runssource: GitHubhomepageJavaMITcommit 9eb1db82e16f
Java, MIT licensed. The project labels itself: cockroachdb, dbms, dbms testing, fuzzing, mariadb, mysql, postgresql and sql.
sqlancer runs. An Argusic agent installed it in 38 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
SQLancer 2.0.0 successfully built with Maven, 51/51 unit tests passed (0 failures, 0 errors), and the fat JAR ran against SQLite executing thousands of queries via the NoREC test oracle with 96% statement success rate
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Java 11+ and Maven not pre-installed in container18 minutes
- First Maven 3.9.16 download from dlcdn incomplete (lib/ missing most JARs)15 minutes
- Maven 3.9.9/3.8.8 URLs on dlcdn.apache.org returned 4042 minutes
- PKIX cert warnings for maven.java.net repos (non-blocking)
- Install time
- 38 minutes
- Cold machine to finish
- 39 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- mvn test -Dtest=... returned 51 tests run, 0 failures, 0 errors; java -jar target/sqlancer-2.0.0.jar --num-threads 1 --timeout-seconds 15 sqlite3 --oracle NoREC ran and executed 7294 queries with 96% success rate
- Model tokens used
- 232,603
- Exact commit tested
- 9eb1db82e16f
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
4. PKIX certificate warnings for java.net repos → non-blocking warnings, build succeeded anyway tokens used 232,603 Here's a summary of what was done: **Installation**: Java 11 (Adoptium Temurin) and Maven 3.9.16 were downloaded from the archive dire… **Tests**: `mvn test` was run for all non-DBMS unit tests (`TestRandomly`, `TestExpectedErrors`, `T… **Runtime verification**: `java -jar target/sqlancer-2.0.0.jar --num-threads 1 --timeout-seconds 15… **Issues encountered and resolved**: 1. Java 11+ and Maven not pre-installed → downloaded Temurin JDK 11 and Apache Maven 3.9.16 2. Maven download from dlcdn.apache.org was incomplete (missing JARs) → re-downloaded from archive.… 3. Maven 3.9.9/3.8.8 URLs returning 404 → used 3.9.16 from archive 4. PKIX certificate warnings for java.net repos → non-blocking warnings, build succeeded anyway
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 38 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
cockroachdbdbmsdbms-testingfuzzingmariadbmysqlpostgresqlsqlsqlitetestingtidb
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/sqlancer)Questions
- Does sqlancer run?
- Yes. sqlancer runs. Argusic installed and launched it on a clean machine in 38 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test sqlancer?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9eb1db82e16f. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test sqlancer?
- The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does sqlancer take to install?
- 38 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does sqlancer need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing sqlancer?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for sqlancer?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.