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

   ## Verification evidence
   
   **CI (current head)**: head SHA `2f189cb5165cbc4958e5cb88c1b4a24e5590c249` 
has exactly one workflow run — "CI" (pull_request), run id 35478307449, 
conclusion `startup_failure`, 0 check-runs / 0 statuses on the head commit. 
Upstream CI startup_fails for every branch/PR in this repository 
(infrastructure-level, not caused by this change); local verification below 
substitutes for it.
   
   **Red (fix reverted, test kept)**: `mvn test 
-Dtest=ToolPlatformCapabilityTest` on the baseline → `Tests run: 1, Failures: 
0, Errors: 1` — `ToolExecutionException: Capability lookup requires a bound 
Instance`, the exact production error.
   
   **Green**: same command with the fix → `Tests run: 1, Failures: 0, Errors: 
0`.
   
   **Related suites** (same run batch): ClusterListToolHandlerTest 2/2, 
ToolCatalogTest 5/5, ToolInstanceRoutingTest 4/4 — total 12 run / 0 failures / 
0 errors.
   
   **Full backend suite**: `SPRING_PROFILES_ACTIVE=dev mvn clean test` (the dev 
profile wires the H2 datasource the integration tests need) → **2396 tests, 1 
failure**. The failure is 
`AuthServiceSessionOverviewIntegrationTest.listActiveSessionsForUserReturnsOnlyThatUsersActiveSessionDetailsTest`
 (asserts `idleSeconds >= 60` and observed 59 — a wall-clock second boundary). 
It is pre-existing: the identical failure reproduces on pristine 
`origin/master` (verified in a clean worktree), and the class passes 3/3 when 
isolated on this branch.
   
   **Baseline reference**: `origin/master` @ d50ffecc under the same profile = 
2395 tests / 0 failures on the baseline run earlier this session; this branch 
adds 1 test → 2396.
   
   **Diff self-check**: `git show --numstat 2f189cb5` → 
`ToolCapabilityFilter.java +8/−0`, `ToolPlatformCapabilityTest.java +107/−0`. 
Two files, 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