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

   ### Evidence (recorded at the PR head)
   
   1. **Head / diff self-check** — `fix/asset-preview-failure-state` @ 
`16160cb5`, one commit; `git show --numstat` = `AlertRuleAssetList.tsx 19/0`, 
`GrafanaDashboardList.tsx 19/0`, `AlertRuleAssetList.test.tsx 22/0`, 
`GrafanaDashboardList.test.tsx 28/0`. No unrelated file touched.
   2. **Red on base** — with only the two test files added on `7ce9a682`, both 
new cases fail: `TestingLibraryElementError: Unable to find role="button" and 
name `/Retry|重试/``.
   3. **Green on branch** — `npx vitest run 
src/components/__tests__/AlertRuleAssetList.test.tsx 
src/components/__tests__/GrafanaDashboardList.test.tsx` → `Test Files 2 passed 
(2)`, `Tests 21 passed (21)`.
   4. **Full suite on branch** — `npx vitest run --maxWorkers=4` → `Test Files 
134 passed (134)`, `Tests 1237 passed (1237)` (measured on this branch alone; 
the `--maxWorkers=4` form is the one that is stable in this sandbox).
   5. **Build / types / lint on branch** — `npx tsc -b` clean, `npx eslint <the 
4 changed files>` clean, `npm run build` → `✓ built in 11.21s`.
   6. **CI** — no workflow run was created for this head SHA (`gh pr view 4734 
--json statusCheckRollup` → 0 checks; `mergeStateStatus: CLEAN`). The 
repository's CI workflow is failing to start for everyone: the newest runs 
repo-wide are `CI pull_request startup_failure` (e.g. 35576031888 @ 
2026-09-21T08:04:50Z), so there is no CI signal to report for this change — the 
local commands above are the evidence.
   
   Duplicate check before submission: no open PR or issue covers a failed 
asset/dashboard preview (`/tmp/open_prs.tsv`, `/tmp/open_issues.tsv`, and the 
project's own bug log were searched; the closest matches are other "failure has 
no surface" reports on different pages).
   


-- 
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