erda tested by Argusic Runner

What the test found

Go 1.24.13 installed from extracted debs, go.mod edited with coreos/bbolt replace, erda-proto-go replace removed (uses remote v1.4.0), volume-provisioner (70 MB binary) builds and runs --help/--providers successfully, and 5 test packages pass: pkg/arrays (0.010s), pkg/goroutinepool (2.507s), pkg/envconf (0.009s), pkg/assert (0.018s), tools/cli/command (0.017s)

Volume-provisioner is the only component that builds (no apistructs/bundle/erda-proto-go dependencies that the remote v1.4.0 is missing). The other 15+ components all depend on apistructs which imports erda-proto-go packages like core/file/pb, core/messenger/eventbox/pb, core/pipeline/pipeline/pb, etc. that are not in the remote v1.4.0 release. Generating them locally with gohub produces code that cross-references other generated types inconsistently. The full build-all pipeline would require gohub to be pre-installed and run on all proto directories in sequence, plus git submodule setup for external protos (e.g. opentelemetry-proto). Since no Kubernetes cluster is present, 'running' means the binary starts and prints its provider list.

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

Runs with mocksall runs of erda

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.