rune
Rune: Native UI framework
Could not verifysource: GitHubRustMITcommit 565de6bb8a34
Rust, MIT licensed.
Argusic could not get rune running. An Argusic agent installed it in 32 minutes and hit 7 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The Rune Rust GPU UI framework compiles successfully across the entire workspace (cargo check --workspace --all-targets passes). The rune-motion spring animation library (68/69 tests pass), rune-ref reference renderer (12/12 pass), rune-kit component library (134/135 pass, 1 pre-existing markdown streaming edge case), procwatch memory/cpu gauge library (1/1 pass), and rune-register (1 doc test pass) all pass.
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 50 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. 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 Vulkan ICD available; GPU-dependent tests cannot run5 minutes
- rune lib test binary linking runs out of memory (SIGKILL) with 8GB limit5 minutes
- No disk space (40GB filled during builds)3 minutes
- Missing libxkbcommon-dev package prevents linking without workaround2 minutes
- rune-motion: animated_retarget_golden hash mismatch (10396150247033498793 vs expected 15969925884686696054)
- rune-kit markdown: an_open_span_never_shows_its_markers test fails
- Install time
- 32 minutes
- Cold machine to finish
- 62 minutes
- Errors hit and fixed
- 7 hit, 7 fixed with no human help
- How the result was proved
- cargo check --workspace --all-targets exited 0 with only 2 minor dead_code warnings. cargo test successes across rune-motion (68/69), rune-ref (12/12), rune-kit --lib (134/135), procwatch (1/1), rune-register (1/1), and ~40 rune integration test files (~150+ tests passed individually)
- Model tokens used
- 507,963
- Exact commit tested
- 565de6bb8a34
- 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
- Whether it works at all
- this run verified nothing, so this page makes no claim either way
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
rune-staging: 0 tests rune-i18n: 0 tests rune integration tests (non-GPU): ~150+ passed across ~40 test files === Known issues === 1. No Vulkan ICD available - GPU-dependent tests skip (need mesa-vulkan-drivers package) 2. libxkbcommon-dev not installed - workaround: symlink + -L flag 3. OOM when linking the rune lib test binary (~490MB) - need >8GB RAM or lld/mold linker 4. 3 pre-existing test failures unrelated to environment Now let me calculate the total time elapsed since I started. tokens used 507,963 Now let me calculate the total time elapsed since I started.
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 7 errors without a human stepping in, which says the failures are documented well enough to solve.
- 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
- An agent with no time limit did not get it running.
- Took 32 minutes to install, slower than the median of the 17 comparable projects Argusic has measured.
Of the 18 Rust projects Argusic has installed and timed, rune was the 17th fastest to reach a running state, and 17 of 18 reached one at all.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Did not run | 20.00 | 0.61 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.30 |
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/rune)Questions
- Does rune run?
- Argusic could not verify that rune runs. Argusic installed and launched it on a clean machine in 32 minutes, hitting 7 errors on the way, and recorded the session.
- How did Argusic test rune?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 565de6bb8a34. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test rune?
- The run that produced this verdict cost $0.30: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does rune take to install?
- 32 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 rune need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing rune?
- 7 things broke in the recorded run, and 7 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does rune compare with the alternatives?
- Of the 18 Rust projects Argusic has installed and timed, rune was the 17th fastest to reach a running state, and 17 of 18 reached one at all.
- Where is the evidence for rune?
- 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.