mopidy
Mopidy is an extensible music server written in Python
Runssource: GitHubhomepagePythonApache-2.0commit 0b258eb6c7fd
Python, Apache-2.0 licensed. The project labels itself: mopidy, music player and python.
mopidy runs. An Argusic agent installed it in 34 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Mopidy CLI works with GStreamer 1.24.2; all 1192 tests pass; pycairo/pygobject built from source against extracted dev packages in a local sysroot
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 46.7 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.
- pygobject/pycairo build failed: missing system deps (cairo, glib, gobject-introspection, dev headers)25 minutes
- Missing liborc-0.4.so.0 for GStreamer plugin loading3 minutes
- GStreamer 1.26.2 required but Ubuntu 24.04 only has 1.24.22 minutes
- GStreamer plugin scanner fork lost LD_LIBRARY_PATH, failed to load plugins2 minutes
- Missing libdw.so.1 for GStreamer ELF handling2 minutes
- Install time
- 34 minutes
- Cold machine to finish
- 22 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- GI_TYPELIB_PATH=/work/repo/.sysroot/usr/lib/x86_64-linux-gnu/girepository-1.0 LD_LIBRARY_PATH=/work/repo/.sysroot/usr/lib/x86_64-linux-gnu GST_PLUGIN_SYSTEM_PATH=/work/repo/.sysroot/usr/lib/x86_64-linux-gnu/gstreamer-1.0 GST_REGISTRY_FORK_DISABLE=yes .venv/bin/pytest --tb=line -q => 1192 passed, mopidy --version => 0.1.dev1+g0b258eb6c, mopidy --help => Usage header with config/deps/help/version commands
- Model tokens used
- 809,935
- Exact commit tested
- 0b258eb6c7fd
- 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
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 3, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
╭─ Commands ───────────────────────────────────────────────────────────────────╮
│ config Display currently active configuration. │
│ deps Display installed extensions and their dependencies. │
│ --help (-h) Display this message and exit. │
│ --version Display application version. │
╰──────────────────────────────────────────────────────────────────────────────╯
All 1192 tests pass and the CLI works. Here's my final report:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 34, "e…
tokens used
809,935
All 1192 tests pass and the CLI works. Here's my final report:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 34, "e…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 34 minutes.
- Recovered from all 5 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 Apache-2.0, as reported by its host.
- Measured 3 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.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 3/3 | Runs | 100.00 | 0.32 | |
| Argusic Runner | 2/3 | Did not run | 20.00 | 0.42 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.28 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mopidy)Questions
- Does mopidy run?
- Yes. mopidy runs. Argusic installed and launched it on a clean machine in 34 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test mopidy?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 0b258eb6c7fd. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test mopidy?
- The run that produced this verdict cost $0.32: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mopidy take to install?
- 34 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 mopidy need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mopidy?
- 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 mopidy?
- All 3 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.