mysql
Go MySQL Driver is a MySQL driver for Go's (golang) database/sql package
Runs with mockssource: GitHubhomepageGoMPL-2.0commit 789a82a35d04
Go, MPL-2.0 licensed. The project labels itself: database, go, mariadb, mysql, mysql driver and sql.
mysql runs, with stand-ins for the services it depends on. An Argusic agent installed it in 9.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Go MySQL driver builds cleanly; all 111 self-contained unit tests pass with 0 failures; a custom mock MySQL server on a dynamic port proved the driver's handshake, authentication, ping, and text-query execution work against a live TCP connection.
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 92 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.
- No MySQL server available in container for integration tests5 minutes
- Go compiler not found in environment2 minutes
- Install time
- 9 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- go test -count=1 ./... exited 0 with 111 passed, 71 skipped (need real MySQL), 0 failed. A standalone Go program connecting to a protocol-mock MySQL server confirmed: Ping OK, SELECT VERSION returned '8.0.46-mock', SELECT DATABASE returned 'gotest'.
- Model tokens used
- 673,001
- Exact commit tested
- 789a82a35d04
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
111 ---skip--- 71 ---fail--- 0 Let me compute elapsed time and compute the final report exec /bin/sh -lc 'echo "Start: 1790417869, End: 1790418438, Diff: $((1790418438 - 1790417869)) seconds =… succeeded in 0ms: Start: 1790417869, End: 1790418438, Diff: 569 seconds = 9 minutes tokens used 673,001
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
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MPL-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 9.5 minutes to install, slower than the median of the 18 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 19 database projects Argusic has installed and timed, mysql was the 17th fastest to reach a running state, and 16 of 19 reached one at all.
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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.09 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mysql)Questions
- Does mysql run?
- mysql runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 9 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test mysql?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 789a82a35d04. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test mysql?
- The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mysql take to install?
- 9.5 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 mysql need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mysql?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does mysql compare with the alternatives?
- Of the 19 database projects Argusic has installed and timed, mysql was the 17th fastest to reach a running state, and 16 of 19 reached one at all.
- Where is the evidence for mysql?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.