oscerd commented on PR #26677:
URL: https://github.com/apache/camel/pull/26677#issuecomment-5764763198
Ready for another look — all six threads are addressed and CI is green on
both JDKs.
The earlier red was infrastructure, not the changeset: the mvnd bootstrap
step never reached a
compiler.
```
Exception in thread "main" java.io.IOException: Server returned HTTP
response code: 429
for URL:
https://repo.maven.apache.org/maven2/org/apache/maven/apache-maven/3.9.16/apache-maven-3.9.16-bin.zip
```
Re-run of the same commit passed unchanged.
Summary of what moved since @davsclaus's review:
- `OpaWasmBundleBuilderTest` → `OpaWasmBundleBuilderIT`, plus an
`opa-it-test` failsafe profile in
`camel-test-infra-opa` modelled on `camel-test-infra-jaeger`. You were
right that the `skipITs`
guard only fires when someone passes it explicitly — a plain `mvn install`
of that module was still
reaching for Docker, which is the same mistake this PR exists to fix, one
module over.
- `acceptsABareModuleAsWellAsTheBundleTarball` untars `policy.wasm` out of
the compiled bundle, so
the bare-`.wasm` branch of `loadPolicy` is still covered now that the
committed binaries are gone.
- `@Timeout(60)` restored on the pool-reuse test, and
`isInstanceOf(Map.class)` +
`containsEntry("allow", true)` restored on the decision-object test.
- `getResourceAsStream()` null now throws naming the missing resource
instead of NPE-ing in
`@BeforeAll`.
_Claude Code on behalf of @oscerd_
--
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]
