atiaomar1978-hub commented on PR #25474: URL: https://github.com/apache/camel/pull/25474#issuecomment-5287154245
## CI failure analysis (run [31728855842](https://github.com/apache/camel/actions/runs/31728855842)) This is **not** the same issue as the earlier **“Fail if there are uncommitted changes”** failure ([run 31708909970](https://github.com/apache/camel/actions/runs/31708909970)). That was fixed in `7a83ef3` (regenerated BOM + endpoint DSL files). On this run, the uncommitted-changes check **passed**. ### Actual failure The **Java 25** `Build and test` job failed on **`camel-pqc`**, which is unrelated to the Alibaba Phase 2 changes: ``` Failed to execute goal maven-surefire-plugin:test on project camel-pqc ``` Failing tests (JDK 25 only): - `PQCSignatureOnlyKeyStoreTest.testSignAndVerify` - `PQCSignatureWithKeyStoreTest.testSignAndVerify` Root cause: ``` java.security.InvalidKeyException: unknown private key passed to ML-DSA ``` The same tests **pass on JDK 17** in this PR’s CI run. ### Why `main` is green but PR CI fails Recent **Main build** runs on `main` are passing (e.g. [run 31742480526](https://github.com/apache/camel/actions/runs/31742480542)). That does **not** mean `camel-pqc` is healthy on JDK 25 — it means `main` CI usually **does not run** those tests: 1. **`regen.sh`** runs with `-DskipTests` (compile only). 2. **Incremental `mvn test`** only tests modules changed in the last push. Typical `main` commits (e.g. TUI-only changes) never touch `camel-pqc`. PR CI pulls in a much wider reactor when BOM/catalog/endpoint DSL files change (Scalpel reports ~600 affected modules), so **`camel-pqc` gets tested here even though this PR does not modify it**. ### Not caused by this PR The same JDK 25 `camel-pqc` failure appeared today on **other unrelated PRs**, for example: - Dependabot log4j bump ([run 31737929643](https://github.com/apache/camel/actions/runs/31737929643)) - CAMEL-24392 SFTP fix ([run 31719954858](https://github.com/apache/camel/actions/runs/31719954858)) This looks like a **pre-existing JDK 25 + BouncyCastle ML-DSA keystore** issue on `main`, not something introduced by the Alibaba Phase 2 work. ### Suggested next steps - Re-run CI (Java 17 already passes `camel-pqc` in this run). - Track/fix upstream: ML-DSA keystore tests failing on JDK 25 (`PQCSignatureOnlyKeyStoreTest`, `PQCSignatureWithKeyStoreTest`). No changes to the Alibaba Phase 2 code are required for this failure. ---Here is a comment you can paste on PR #25474: --- ## CI failure analysis (run [31728855842](https://github.com/apache/camel/actions/runs/31728855842)) This is **not** the same issue as the earlier **“Fail if there are uncommitted changes”** failure ([run 31708909970](https://github.com/apache/camel/actions/runs/31708909970)). That was fixed in `7a83ef3` (regenerated BOM + endpoint DSL files). On this run, the uncommitted-changes check **passed**. ### Actual failure The **Java 25** `Build and test` job failed on **`camel-pqc`**, which is unrelated to the Alibaba Phase 2 changes: ``` Failed to execute goal maven-surefire-plugin:test on project camel-pqc ``` Failing tests (JDK 25 only): - `PQCSignatureOnlyKeyStoreTest.testSignAndVerify` - `PQCSignatureWithKeyStoreTest.testSignAndVerify` Root cause: ``` java.security.InvalidKeyException: unknown private key passed to ML-DSA ``` The same tests **pass on JDK 17** in this PR’s CI run. ### Why `main` is green but PR CI fails Recent **Main build** runs on `main` are passing (e.g. [run 31742480526](https://github.com/apache/camel/actions/runs/31742480542)). That does **not** mean `camel-pqc` is healthy on JDK 25 — it means `main` CI usually **does not run** those tests: 1. **`regen.sh`** runs with `-DskipTests` (compile only). 2. **Incremental `mvn test`** only tests modules changed in the last push. Typical `main` commits (e.g. TUI-only changes) never touch `camel-pqc`. PR CI pulls in a much wider reactor when BOM/catalog/endpoint DSL files change (Scalpel reports ~600 affected modules), so **`camel-pqc` gets tested here even though this PR does not modify it**. ### Not caused by this PR The same JDK 25 `camel-pqc` failure appeared today on **other unrelated PRs**, for example: - Dependabot log4j bump ([run 31737929643](https://github.com/apache/camel/actions/runs/31737929643)) - CAMEL-24392 SFTP fix ([run 31719954858](https://github.com/apache/camel/actions/runs/31719954858)) This looks like a **pre-existing JDK 25 + BouncyCastle ML-DSA keystore** issue on `main`, not something introduced by the Alibaba Phase 2 work. ### Suggested next steps - Re-run CI (Java 17 already passes `camel-pqc` in this run). - Track/fix upstream: ML-DSA keystore tests failing on JDK 25 (`PQCSignatureOnlyKeyStoreTest`, `PQCSignatureWithKeyStoreTest`). No changes to the Alibaba Phase 2 code are required for this failure. --- -- 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]
