git-fame-rb

A command-line tool that helps you summarize and pretty-print collaborators based on contributions

Runssource: GitHubRubyMITcommit f94948c58673

Ruby, MIT licensed. The project labels itself: code statistics, command line tool, contributor analysis and git.

git-fame-rb runs. An Argusic agent installed it in 12 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Ruby gem git-fame v3.3.0 compiles, runs against the repository producing author statistics, and passes its full RSpec test suite (65 examples, 0 failures)

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

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.11 (measured)
recorded runs
1
last tested
stars
958
forks
72
open issues
24
watchers
15
size
1 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 git-fame-rb, 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.

  • Ruby not installed in container5 minutes
  • Ruby build failed on missing dev headers (zlib1g-dev, libyaml-dev, libffi-dev)4 minutes
  • Bundler failed with 'cannot load such file -- zlib'1 minute
  • psych extension failed to load (missing libyaml)1 minute
  • fiddle extension build failed (libffi.a not compiled with -fPIC)1 minute
Install time
12 minutes
Cold machine to finish
12 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
bundle exec rspec passed 65 examples, 0 failures; git-fame --version returned v3.3.0; git-fame on the repo produced a table with 1 author, 2394 lines, 1 commit, 40 files
Model tokens used
149,173
Exact commit tested
f94948c58673
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.

 succeeded in 0ms:
f94948c Release 3.3.0 (#157)
All systems verified. Here's the final report:
- 65/65 RSpec tests pass
- CLI responds to `--version` and `--help`
- Runs against this repo producing valid author stats
tokens used
149,173
All systems verified. Here's the final report:
- 65/65 RSpec tests pass
- CLI responds to `--version` and `--help`
- Runs against this repo producing valid author stats

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 12 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 MIT, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

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 byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.11

Topics (from GitHub)

code-statisticscommand-line-toolcontributor-analysisgit

Embed the badge

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

[![Tested by Argusic](https://argusic.com/badge/git-fame-rb.svg)](https://argusic.com/subject/git-fame-rb)

Questions

Does git-fame-rb run?
Yes. git-fame-rb runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test git-fame-rb?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit f94948c58673. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test git-fame-rb?
The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does git-fame-rb take to install?
12 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 git-fame-rb need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing git-fame-rb?
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 git-fame-rb?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion