spring-cloud-stream tested by Argusic Runner

What the test found

Spring Cloud Stream 5.1.0-SNAPSHOT compiles, installs and passes 958 tests (0 failures) across core, kafka, kafka-streams, pulsar and schema-registry modules; a real RabbitMQ 3.12.1 broker runs locally and serves AMQP and its management API; only the Rabbit binder integration suite cannot run because its Testcontainers harness requires a Docker daemon absent from this container.

JDK 17 + Maven went in as user-space tools (no root available). README's canonical './mvnw install' fails only at the Docker-gated rabbit-binder module; with just that module excluded, mvn install BUILD SUCCESS across 25/25 modules. Verified: core 41, spring-cloud-stream-test-binder 2, kafka-core 16, kafka 169, kafka-streams 122, pulsar 74 run (14 docker-gated skipped), schema-registry 47 run (20 skipped) - aggregate 958 tests run, 0 failures, 110 skipped; my own AMQP client published and consumed 'hello' against the local RabbitMQ 3.12.1 broker (mgmt API HTTP 200). The 10-20 skips per module are the testcontainers container-gated suites which auto-skip via @Testcontainers(disabledWithoutDocker=true).

Argusic installed spring-cloud-stream in 61 minutes and launched it; verification reached Verified running for real. 4 of 4 recorded errors were worked through (see the timeline below).

Runsall runs of spring-cloud-stream

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.