Yes. zeppelin runs. Argusic installed and launched it on a clean machine in 37 minutes, hitting 3 errors on the way, and recorded the session.

How did Argusic test zeppelin?

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

What did it cost to test zeppelin?

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

How long does zeppelin take to install?

37 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 zeppelin need a GPU?

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

What goes wrong when installing zeppelin?

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

Where is the evidence for zeppelin?

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.

zeppelin

Web-based notebook that enables data-driven, interactive data analytics and collaborative documents with SQL, Scala and more.

Runssource: GitHub homepageJavaApache-2.0commit 703fe6763f6f

Java, Apache-2.0 licensed. The project labels itself: big data, database, flink, java, javascript, nosql, scala and spark.

zeppelin runs. An Argusic agent installed it in 37 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Apache Zeppelin 0.13.0-SNAPSHOT builds from source with Maven and JDK 11, the server starts on port 18080 responding HTTP 200 on /api/version, and 132 interpreter-unit tests plus 21 server-unit tests pass fully.
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 96 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 96 / 100
cost of the verifying run: $0.22 (measured)
recorded runs: 2
last tested: 2026-09-16
stars: 6,660
forks: 2,837
open issues: 63
watchers: 296
size: 112 MB
created: 2015-03-25
last push: 2026-09-21

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 zeppelin, 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.

Server integration tests need pre-built interpreter directories5 minutes
No JDK installed in container2 minutes
copy-dependencies fails on reactor artifacts when using test without prior package1 minute

Install time: 37 minutes
Cold machine to finish: 37 minutes
Errors hit and fixed: 3 hit, 3 fixed with no human help
How the result was proved: curl -s -w '%{http_code}' http://localhost:18080/api/version returned 200 with version JSON over 3 consecutive checks; mvn test -pl zeppelin-interpreter --am returned 132 tests 0 failures; mvn test -pl zeppelin-server --am -Dtest=ZeppelinConfigurationTest,ConfigurationServiceTest,CacheContolFilterTest returned 21 tests 0 failures
Model tokens used: 151,592
Exact commit tested: 703fe6763f6f
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.

- `zeppelin-server` (unit tests not needing MiniZeppelinServer): **21 tests, 0 failures, 0 errors**…
- Server integration tests (NotebookRestApiTest, ZeppelinRestApiTest, NotebookServerTest, etc.) fai…
**Server launch**: Started on `localhost:18080`, confirmed with:
```sh
curl -s -w "\nHTTP:%{http_code}\n" http://localhost:18080/api/version
```
Returns `{"status":"OK","message":"Zeppelin version","body":{"git-commit-id":"703fe67","git-timesta…
**Errors encountered and fixes**:
1. **No JDK installed** — downloaded Adoptium Temurin JDK 11 from adoptium.net, extracted to `/home…
2. **Missing interpreter directories for tests** — built `markdown`, `python`, `shell`, `angular` m…
3. **Server JAR vs directory classpath issue** — the `copy-dependencies` plugin won't copy reactor …
The Zeppelin 0.13.0-SNAPSHOT build and server operate as expected from source on this Ubuntu 24.04 …

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 37 minutes.
Recovered from all 3 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 2 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.

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	Runs with mocks	92.00	0.41	2026-09-16 17:28 UTC
Argusic Runner	1/3	Runs	100.00	0.22	2026-09-11 19:52 UTC

Topics (from GitHub)

big-data database flink java javascript nosql scala spark zeppelin

Embed the badge

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

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

Questions

Does zeppelin run?: Yes. zeppelin runs. Argusic installed and launched it on a clean machine in 37 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test zeppelin?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 703fe6763f6f. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test zeppelin?: The run that produced this verdict cost $0.22: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does zeppelin take to install?: 37 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 zeppelin need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing zeppelin?: 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for zeppelin?: 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.