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

   ## Verification evidence
   
   - **CI**: run `35551730010` ("CI", event `pull_request`) at head `1c3071f5` 
— conclusion `startup_failure` (the workflow never starts; repository-level 
issue, other open PRs from the same window show the same). `check-runs`: 0; 
combined status: no statuses. All results below are from local runs of the 
exact head commit.
   - **Red** (new regression on master source): `Tests run: 1, Failures: 1` — 
Mockito recorded `record("FAIL_ALERT_NOTIFICATION", "ALERT_NOTIFICATION", "8", 
null, "alertId=9, channel=dingtalk", "FAILURE", "DingTalk rejected webhook: 
keywords not in content")` while the test requires `"FAILED"`.
   - **Module**: `mvn -o -Dtest='NotificationOutboxServiceTest' test` → `Tests 
run: 26, Failures: 0, Errors: 0` (25 pre-existing + 1 new).
   - **Full backend suite** (this branch, head `1c3071f5`): 
`SPRING_PROFILES_ACTIVE=dev mvn -o test` → `Tests run: 2415, Failures: 0, 
Errors: 0, Skipped: 0`, `BUILD SUCCESS`. Pristine master baseline on this 
machine: 2414 passing; 2415 = baseline + 1 new test, zero new failures.
   - **Build**: `mvn -o -DskipTests package` → `BUILD SUCCESS`, 
`target/rocketmq-studio-1.0.0.jar` produced (covers the `backend-build` job's 
compile/package steps; the CI job itself cannot start, see above). `mvn -o 
checkstyle:check` → clean.
   - **Diff self-check** (`git diff --numstat 
origin/master..fix/notification-audit-result-vocabulary`): `3/1 
server/src/main/java/.../ops/alert/NotificationOutboxService.java`, `38/0 
server/src/test/java/.../ops/alert/NotificationOutboxServiceTest.java` — 2 
files, no unrelated changes. Single commit `1c3071f5`.
   


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