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

   ### CI status of this PR
   
   `Backend Tests (Java 21)` — **fail on the pre-existing H2 flake**: 
`ResourceOwnershipGuardTest.migrationConcurrentStartupIsIdempotentTest:566 00bb 
org.h2.jdbc.JdbcSQLNonTransientException: General error: 
"java.util.ConcurrentModificationException"` (run 37959977654, job 
113920044100). It is the known flaky concurrency test tracked by #5302 and is 
unrelated to this diff, which changes no persistence code; the same job passes 
on the sibling PRs of this batch (e.g. #5886, run 37959764821).
   
   The four remaining red jobs are red for every branch, including 
`rocketmq-studio` itself:
   
   - `Backend Build (Java 21)` — the `binary-license-gate` antrun step fails on 
a list of third-party jars (`spring-ai-*`, `swagger-ui`, `tencentcloud-sdk-*`, 
`zstd-jni`, ... : "missing complete upstream LICENSE/COPYING; a POM name or 
link is not a substitute"). This PR touches no build configuration; tracked by 
#5341.
   - `Frontend Build (Node 20)` / `Frontend Docker Build` — the frontend 
licence manifest check fails the same way on branches that do not touch `web/` 
at all; tracked by #5346.
   - `rmqctl Build (Go)` — `cmd` `TestMessageQueryCompletenessWarningTest` yaml 
subtests: `got {"items":[{"size":"3","storeTime":"1",...}]}, want 
{"size":3,"storeTime":1,...}`, i.e. the YAML renderer writes numbers as quoted 
strings where the test expects integer literals. Reproduced locally with `cd 
rmqctl && go test ./cmd/` from a checkout whose `rmqctl/` tree is 
byte-identical to `rocketmq-studio`'s (this PR does not touch the CLI), and 
already owned by open PR #5850 ("keep yaml numbers unquoted").
   


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