unbridled-41 commented on PR #4263:
URL:
https://github.com/apache/rocketmq-dashboard/pull/4263#issuecomment-5649968346
## Verification evidence
- **CI (this head)**: run 34730761774 ("CI", `pull_request`, head
`e9455a81008a1ca58b1bd2907826ff2c26b37e97`) — conclusion `startup_failure`,
check-runs 0. Upstream workflow fails at startup for every branch (unapproved
Docker actions, #4136); local verification below covers the compile/test/build
surface.
- **Red (actual output, on 6c24d2ed code)**: `UserManagement.test.tsx >
exports users matching the committed search, not live input` — `waitFor` timed
out because `downloadStudioUsers` (the export API) was called with `search:
'alpha-beta'` (the live input) instead of `search: 'alpha'` (the committed
value). Summary `Tests 1 failed | 6 passed (7)`. Verified with the fix stashed;
restored for the green run.
- **Module tests (after fix)**: `UserManagement.test.tsx` **7/7 passed**,
re-run after lint-staged's prettier reformat.
- **Full suite + baseline**: `npx vitest run` on this branch → **982 tests,
979 passed, 3 failures** — all in untouched files of the known load-fragile
family (`MetricsExplorer.test.tsx > restores profile, range, and source from
query history`, `ConsumerPage.test.tsx > shows group health diagnostics...` +
`> invalidates the reset preview...`). Isolation re-runs: MetricsExplorer
**25/25**, ConsumerPage **31/31** — load fragility, not regressions. The new
test passes inside the full run. (Baseline 6c24d2ed recorded 982 tests with the
same fragile-family failures across rounds 8-13.)
- **Build**: `npm run build` succeeds (`✓ built in 9.67s`); `npx tsc -b`
clean; `npx eslint` clean on both touched files (0 error / 0 warning).
- **Diff self-check**: `git show --numstat` =
`web/src/pages/studio/UserManagement.tsx +4/−2`,
`web/src/pages/studio/__tests__/UserManagement.test.tsx +36/−0`. 2 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]
