MacNativeGames

Runs with mockssource: GitHubCMITcommit 30a1b93d0776

C, MIT licensed.

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

All 256 tests run without failures (217 passed, 39 skipped as expected on Linux). The build_app.py clonefile function gracefully degrades to shutil.copy2 on non-macOS; the test suite handles Linux-compatible .venv setup, codesign/data_bundle mocking, and lazy imports for missing Python 3.14 modules.

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 86 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
86 / 100
cost of the verifying run
$0.20 (measured)
recorded runs
2
last tested
stars
4,169
forks
585
open issues
89
watchers
21
size
12 MB
created
last push

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.

Time lost to each failure while testing MacNativeGames, 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.

  • test_updates.py symlinked .venv to sys.prefix (/usr) but /usr/bin is read-only; also called step_app without patching data_bundle which runs codesign1.5 minutes
  • build_app.clonefile() failed on Linux because clonefile(2) is macOS-only (undefined symbol: clonefile in libc)1.2 minutes
  • test_build_mod.py's mergeable_overlays() failed because make_romfs_patches imports compression.zstd at module level0.8 minutes
  • test_app_game_data.py used os.stat_result.st_birthtime which does not exist on Linux0.5 minutes
  • test_botw_import.py called step_app which invoked data_bundle and then codesign (macOS-only)0.5 minutes
  • games/botw/scripts/location_markers.py imported sarc_members from make_romfs_patches at module level, which fails without compression.zstd0.5 minutes
Install time
7 minutes
Cold machine to finish
15 minutes
Errors hit and fixed
8 hit, 8 fixed with no human help
How the result was proved
python3 -m unittest discover -s tests exited 0; 256 tests ran, 217 passed, 39 skipped (all expected macOS/Xcode/Python 3.14-only tests)
Model tokens used
641,588
Exact commit tested
30a1b93d0776
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.

7. **`test_botw_import.py`**: Patched `data_bundle` in the test that calls `step_app`
8. **`games/botw/scripts/location_markers.py`**: Made `sarc_members` import lazy to avoid importing…
Now let me provide the final result:
exec
/bin/sh -lc 'cd /work/repo && python3 -m unittest discover -s tests 2>&1 | grep -E "''^Ran|''^OK|''…
 succeeded in 6789ms:
Ran 256 tests in 6.792s
OK (skipped=39)
Let me compute the total time and produce the final report.
tokens used
641,588
Let me compute the total time and produce the final report.

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 6.8 minutes, faster than the median of the 5 comparable projects Argusic has measured.
  • Recovered from all 8 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

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.

Of the 6 C projects Argusic has installed and timed, MacNativeGames was the 3rd fastest to reach a running state, and 5 of 6 reached one at all.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.20
Argusic Runner1/3Unverified80.000.21

Embed the badge

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

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

Questions

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

Discussion