RustWTM

Windows task manager and resource governor written in Rust. Monitor processes, manage resource usage, and keep your PC responsive.

Could not verifysource: GitHubRustMITcommit 1f396ec3785d

Rust, MIT licensed. The project labels itself: cpu limiter, egui, process manager, rust, task manager, windows and windows service.

Argusic could not get RustWTM running. An Argusic agent installed it in 44.7 minutes and hit 6 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The RustWTM workspace cross-compiles from Linux to x86_64-pc-windows-gnu: 8 crates (wtm-sys, wtm-core, wtm-policy, wtm-ipc, wtm-ai, wtm-cli, wtm-service, wtm-gui) all pass type-checking, and the 3 release binaries (CLI, service, GUI) are produced as valid PE executables.

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

At a glance

verdict
Could not verify
Argusic Score
40 / 100
cost of the verifying run
$0.16 (measured)
recorded runs
2
last tested
stars
245
forks
0
open issues
0
watchers
0
created
-
last push
-

Subject data from GitHub, linked at the top of this page. 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 RustWTM, 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.

  • build.rs resource embedding fails due to missing windres and mingw toolchain10 minutes
  • Linking fails: crt2.o and Windows import libraries not found by mingw ld5 minutes
  • libsqlite3-sys C compilation fails: #include_next <stdarg.h> cannot find platform header3 minutes
  • Rust toolchain not installed in container2 minutes
  • windows-future crate fails on Linux host (cfg(windows)-gated function 'submit')1 minute
  • Missing glib-2.0 and other GTK development libraries for native Linux build1 minute
Install time
45 minutes
Cold machine to finish
45 minutes
Errors hit and fixed
6 hit, 6 fixed with no human help
How the result was proved
All 8 crates pass cargo check --all-targets for x86_64-pc-windows-gnu. 3 release binaries built successfully: wtm.exe (3.6 MiB), wtm-service.exe (5.3 MiB), rustwtm.exe (22.0 MiB). All are valid PE executables with MZ magic and PE signature. No compilation errors.
Model tokens used
663,628
Exact commit tested
1f396ec3785d
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
Whether it works at all
this run verified nothing, so this page makes no claim either way

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

      "msg": "Linking fails: crt2.o and Windows import libraries not found by mingw ld",
      "fix": "Created proper --sysroot setup pointing to extracted mingw installation with correct …
      "minutes": 5.0
    }
  ],
  "test_depth": "tier3_none",
  "notes": "This is a Windows-native application (task manager/resource governor). All 8 crates com…
  "verified_how": "All 8 crates pass cargo check --all-targets for x86_64-pc-windows-gnu. 3 release…
  "final_state": "The RustWTM workspace cross-compiles from Linux to x86_64-pc-windows-gnu: 8 crate…
}
tokens used
663,628

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 44.7 minutes.
  • Recovered from all 6 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

  • An agent with no time limit did not get it running.

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 Runner2/3Did not run0.000.02
Argusic Runner1/3Unverified80.000.16

Topics (from GitHub)

cpu-limitereguiprocess-managerrusttask-managerwindowswindows-service

Embed the badge

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

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

Questions

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