supertux runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 18 minutes, hitting 5 errors on the way, and recorded the session.

How did Argusic test supertux?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7852251d827f. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test supertux?

The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does supertux take to install?

18 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 supertux need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing supertux?

5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for supertux?

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.

supertux

SuperTux source code

Runs with mockssource: GitHub homepageC++GPL-3.0commit 7852251d827f

C++, GPL-3.0 licensed. The project labels itself: c plus plus, game, games, opengl, sdl, sdl3 and supertux.

supertux runs, with stand-ins for the services it depends on. An Argusic agent installed it in 18 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

SuperTux builds from source, runs with SDL offscreen video driver, creates a window, initializes the software renderer, and passes all 3 ctest unit tests.
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 56 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs with mocks
Argusic Score: 56 / 100
cost of the verifying run: $0.15 (measured)
recorded runs: 2
last tested: 2026-09-17
stars: 3,150
forks: 608
open issues: 372
watchers: 80
size: 824 MB
created: 2013-11-23
last push: 2026-09-23

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-23. 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.

Time lost to each failure while testing supertux, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

Missing system development packages (SDL3, libpng, zlib, freetype, fmt, glm, physfs, openal, glew, libcurl, libogg, libvorbis)15 minutes
SDL3_ttf required SDL3 >= 3.2.6 but built SDL3 was 3.2.41 minute
GLEW build failed due to missing OpenGL headers and auto-generated sources1 minute
SDL3_image pkg-config file not installed after build0.5 minutes
glm cmake config had broken relative path for include dirs0.5 minutes

Install time: 18 minutes
Cold machine to finish: 29 minutes
Errors hit and fixed: 5 hit, 5 fixed with no human help
Model tokens used: 255,747
Exact commit tested: 7852251d827f
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.

How the result was proved: runs before 2026-09-07 did not record the command used to check the result
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.

All 3 tests pass! Let me clean up and compile the final results.
Let me also check the launch one more time to have it count as successful
exec
/bin/sh -lc 'cd /work/repo/build && LD_LIBRARY_PATH=/work/repo/_inst/lib SDL_VIDEO_DRIVER=offscreen…
 succeeded in 2891ms:
Exit code: 124
Exit 124 is from `timeout` killing it after 3 seconds, which is expected. The app properly initiali…
Now let me calculate the time spent. The main build took about 30 min total (I timed the output rou…
tokens used
255,747
Exit 124 is from `timeout` killing it after 3 seconds, which is expected. The app properly initiali…
Now let me calculate the time spent. The main build took about 30 min total (I timed the output rou…

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

Installed in 18 minutes, faster than the median of the 4 comparable projects Argusic has measured.
Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
Licensed GPL-3.0, as reported by its host.
Measured 2 times, so the result is not a one-off.

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.

Of the 5 c-plus-plus projects Argusic has installed and timed, supertux was the 2nd fastest to reach a running state, and 4 of 5 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	2/3	Did not run	20.00	0.14	2026-09-17 19:42 UTC
Argusic Runner	1/3	Runs with mocks	92.00	0.15	2026-09-05 21:19 UTC

Topics (from GitHub)

c-plus-plus game games opengl sdl sdl3 supertux

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/supertux.svg)](https://argusic.com/subject/supertux)

Questions

Does supertux run?: supertux runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 18 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test supertux?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 7852251d827f. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test supertux?: The run that produced this verdict cost $0.15: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does supertux take to install?: 18 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 supertux need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing supertux?: 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does supertux compare with the alternatives?: Of the 5 c-plus-plus projects Argusic has installed and timed, supertux was the 2nd fastest to reach a running state, and 4 of 5 reached one at all.
Where is the evidence for supertux?: 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.