abstruse
Abstruse is a free and open-source CI/CD platform that tests your models and code.
Runssource: GitHubhomepageGoMITcommit 39de5c2b0e8d
Go, MIT licensed. The project labels itself: cd, ci, continuous delivery, continuous deployment, continuous integration, continuous testing, docker and dockerized.
abstruse runs. An Argusic agent installed it in 10 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Both abstruse-server and abstruse-worker binaries compile and run; the server serves HTTP 200 with the Abstruse CI web UI on port 8765 using SQLite without external dependencies.
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 60 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.
- Build tools (protoc, protoc-gen-go, protoc-gen-go-grpc, statik, wire, reflex) not installed4 minutes
- Go not installed in container2 minutes
- protoc failed due to missing well-known types include path1 minute
- Install time
- 10 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- curl -s -o /dev/null -w '%{http_code}' http://localhost:8765/ returned 200 and HTML body contains 'Abstruse CI'
- Model tokens used
- 58,447
- Exact commit tested
- 39de5c2b0e8d
- 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.
## Final Report **Summary of what was done:** 1. **Go not installed** → downloaded Go 1.21.13 to `/tmp/go` and added to PATH/GOROOT 2. **Missing build tools** → installed protoc (25.1), protoc-gen-go, protoc-gen-go-grpc, statik, wi… 3. **Generated protobuf** → `make protoc` generated `pb/api.pb.go` and `pb/api_grpc.pb.go` (needed … 4. **Built UI** → `npm install` then `npm run build` in `web/abstruse/`, Angular production build s… 5. **Generated embedded assets** → `statik` produced `server/ui/statik.go` 6. **Generated wire injection** → `wire` produced `wire_gen.go` for both server and worker 7. **Built Go binaries** → `make server` and `make worker` produced `build/abstruse-server` (59MB) … 8. **Tests** → `go test ./...` ran — all 49 packages have no test files 9. **Ran server** → launched with `--db-driver sqlite` (no external DB needed), listening on port 8… 10. **Worker verified** → `abstruse-worker --help` prints usage correctly, `abstruse-server version…
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.
- Recovered from all 3 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 did not, or is not known
- Took 10 minutes to install, slower than the median of the 5 comparable projects Argusic has measured.
Of the 6 cd projects Argusic has installed and timed, abstruse was the 4th fastest to reach a running state, and 4 of 6 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 10 minutes after the clone.
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 | 2/3 | Runs | 100.00 | 0.05 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 2.27 |
Topics (from GitHub)
cdcicontinuous-deliverycontinuous-deploymentcontinuous-integrationcontinuous-testingdockerdockerizedservertesting
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/abstruse)Questions
- Does abstruse run?
- Yes. abstruse runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test abstruse?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 39de5c2b0e8d. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test abstruse?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does abstruse take to install?
- 10 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 abstruse need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing abstruse?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does abstruse compare with the alternatives?
- Of the 6 cd projects Argusic has installed and timed, abstruse was the 4th fastest to reach a running state, and 4 of 6 reached one at all.
- Where is the evidence for abstruse?
- 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.