fscrawler
Elasticsearch File System Crawler (FS Crawler)
Runssource: GitHubhomepageJavaApache-2.0commit 8b4db8435639
Java, Apache-2.0 licensed. The project labels itself: crawler, elasticsearch, java and tika.
fscrawler runs. An Argusic agent installed it in 55 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
FSCrawler 3.1-SNAPSHOT builds successfully via Maven, distributable ZIP is packaged, binary launches and shows help/version, and 687 unit tests pass when run with the `-Dtest="*Test"` workaround
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 60 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.
- Default test discovery via `mvn test -DskipIntegTests` reports Tests run: 0 across all modules due to RepeatExecutionTestEngine from randomizedtesting-jupiter interfering with surefire discovery25 minutes
- FsSshPluginTest expects hardcoded file permission bits (33188/16877) but OS returns different values (33204/16893)
- Install time
- 55 minutes
- Cold machine to finish
- 82 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- `mvn clean test -DskipIntegTests -Dtest="*Test" -pl '!plugins/fs-ssh-plugin'` exited 0 with 687 tests passed, 0 failures; binary `--version` printed 3.1-SNAPSHOT
- Model tokens used
- 852,092
- Exact commit tested
- 8b4db8435639
- 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.
**Issues encountered**: 1. Java 21 + Maven 3.9.16 needed manual download — resolved by prior handoff. 2. `mvn test -DskipIntegTests` discovers 0 tests by default — the `randomizedtesting-jupiter` `Repe… tokens used 852,092 All results collected. Here is the final report: **Build**: `mvn clean package -DskipTests -Ddocker.skip -Dossindex.skip -Dspotless.skip=true` — BUI… **Launch**: Binary at `/tmp/fscrawler/fscrawler-distribution-3.1-SNAPSHOT/bin/fscrawler` responds t… **Tests**: 687 unit tests pass with 0 failures when run as `mvn clean test -DskipIntegTests -Dtest=… **Issues encountered**: 1. Java 21 + Maven 3.9.16 needed manual download — resolved by prior handoff. 2. `mvn test -DskipIntegTests` discovers 0 tests by default — the `randomizedtesting-jupiter` `Repe…
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.
- Recovered from all 2 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 did not, or is not known
- Took 55 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.
Of the 12 crawler projects Argusic has installed and timed, fscrawler was the 12th fastest to reach a running state, and 10 of 12 reached one at all.
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 | 100.00 | 0.46 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.20 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/fscrawler)Questions
- Does fscrawler run?
- Yes. fscrawler runs. Argusic installed and launched it on a clean machine in 55 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test fscrawler?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8b4db8435639. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test fscrawler?
- The run that produced this verdict cost $0.46: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does fscrawler take to install?
- 55 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 fscrawler need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing fscrawler?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does fscrawler compare with the alternatives?
- Of the 12 crawler projects Argusic has installed and timed, fscrawler was the 12th fastest to reach a running state, and 10 of 12 reached one at all.
- Where is the evidence for fscrawler?
- 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.