unbridled-41 commented on PR #4568:
URL: 
https://github.com/apache/rocketmq-dashboard/pull/4568#issuecomment-5747184222

   ## Verification evidence
   
   **CI (current head)**: head SHA `0a083b034dbc511c302e024a1501ad0f553b5f67` 
has exactly one workflow run — "CI" (pull_request), run id 35484583000, 
conclusion `startup_failure`, and 0 check-runs on the head commit (upstream CI 
fails at startup for every branch/PR, including maintainers'; 
infrastructure-level, not caused by this change). Local verification below 
substitutes for it.
   
   **Red (baseline = master `d50ffecc` + the new test, fix stashed)**: `mvn -o 
test -Dtest=RocketMQLiteTopicProviderTest` → `Tests run: 15, Failures: 1` —
   - `isSupportedIsTrueWhenAnyOtherMasterAnswersTheLiteProbe` — `Expecting 
value to be true but was false` (master[0] throwing unsupported-code disabled 
the capability although the second master answered).
   
   **Module (green)**: `mvn -o test -Dtest=RocketMQLiteTopicProviderTest` → 
**15/15 passed, 0 failures, 0 errors** (the file's own suite; the list/quota 
per-master degradation regressions live in the sibling PR #4566 and are not 
part of this branch).
   
   **Full suite + baseline**: `SPRING_PROFILES_ACTIVE=dev mvn -o clean test` on 
this exact tree → **`Tests run: 2415, Failures: 0, Errors: 0, Skipped: 0`, 
BUILD SUCCESS** (XML surefire basis). Pristine `origin/master` `d50ffecc` in a 
clean worktree on the identical basis: **2414 tests, 0 failures** — the +1 
delta is exactly the new regression test. Zero new failures.
   
   **Build**: `mvn -o checkstyle:check` → **0 violations**, BUILD SUCCESS 
(compilation covered by the full `clean test` run).
   
   **Diff self-check (`git show --numstat HEAD`)**: `16/2 
server/.../provider/apache/RocketMQLiteTopicProvider.java`, `10/0 
server/.../provider/apache/RocketMQLiteTopicProviderTest.java` — 2 files, 
+26/−2, no unrelated changes.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to