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

   ## Verification evidence
   
   - **CI**: branch head `2343a1525546cadbbcd4abed4d4f43612b3ad358` (PR #4253) 
has exactly one workflow run for this head: "CI" (pull_request event), run 
34709645518, conclusion=startup_failure — the upstream workflow fails at 
startup for every branch in this repository (including recent upstream merges), 
so no check-runs are produced (`check-runs total_count = 0`). This is unrelated 
to the change; all local verification below was run on this head.
   - **Red light (unfixed code)**: with the regression test kept and the 
baseline `UserManagement.tsx` restored, `npx vitest run 
src/pages/studio/__tests__/UserManagement.test.tsx` → `Test Files  1 failed 
(1)`, `Tests  1 failed | 6 passed (7)`, failing item `× clears the create-user 
form after the dialog is dismissed` (username/password still filled after 
cancel+reopen).
   - **Module tests (fixed)**: `npx vitest run 
src/pages/studio/__tests__/UserManagement.test.tsx` → `Tests  7 passed (7)`.
   - **Full suite + baseline**: `npx vitest run` on this head → 120 files, 
`Tests  1 failed | 981 passed (982)`; the single failure is 
`ConsumerPage.test.tsx > shows group health diagnostics…`, a file untouched by 
this branch and a recurring load-fragile case under the parallel suite; re-run 
in isolation → `Tests  31 passed (31)`. Zero failures in files touched by this 
change.
   - **Build**: `npx tsc -b` clean; `npx vite build` succeeds. `npx eslint .` → 
0 errors, 10 warnings, all in files this branch does not touch 
(QueueBrowser.tsx, dlq.tsx, alerts.tsx, systemAlerts.tsx, LiteTopic.tsx).
   - **Diff self-check** (`git show --numstat`): 
`web/src/pages/studio/UserManagement.tsx +4/−1`, 
`web/src/pages/studio/__tests__/UserManagement.test.tsx +18/−0` — 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