runn tested by Argusic Runner

Attempt 2 of 3 · Runs with mocks · Argusic Score 92.0 of 100

all runs of runnapi-testingautomationbufbuf-schema-registrychrome-devtools-protocoldb-client

Session recording

Loading recording...

Download the original recording · fingerprint f808126e1c8b73a9...

What the test found

runn builds and runs: binary reports version 1.11.1, local + mock-github runbooks run with 0 failures, internal/fs GitHub/gist fetch tests pass against a locally stood-up schema-correct GitHub Enterprise mock, HTTP GitHub-API test passes end-to-end against that mock; Chrome and Docker daemon not available in the container so CDP tests and Docker-container-backed tests remain failing, and real GitHub credentials are still required for the original un-mocked TestFetchPaths/TestHTTPRunnerRunUsingGitHubAPI against api.github.com and for TestUseParentStore.

Verified: make build ok (runn v1.11.1); full suite unit PASS for all non-CDP, non-Docker, non-real-credential tests (internal/fs ok, HTTP/gRPC/SSH host rules pass, HTTP GitHub-API test pass); CLI E2E ok via mock: runn run github://...runn_0_success.yml => 1 scenario 0 failures; quickstart E2E: runn new --and-run + runn run /tmp/demo/http.yml vs live Python HTTP server => 1 scenario 0 failures; go vet clean; only Docker- and Chrome-requiring tests still fail.

Argusic installed runn in 14 minutes and launched it; verification reached Verified with mock services. 5 of 5 recorded errors were worked through (see the timeline below).

Runs with mocksall runs of runn

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.

Error and fix timeline

No errors were recorded for this run.

Discussion