-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix spring-web test failure #20291
Fix spring-web test failure #20291
Conversation
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building 51a867a
Full information is available in the Build summary check run. Failures⚙️ Gradle Tests - JDK 11 Windows #- Failing: integration-tests/gradle
📦 integration-tests/gradle✖
|
Was this intended to fix the Asking because it was fixed with #20271 |
I did not notice that, but do we really want to be adding a resteasy-classic SPI artifact to a resteasy-reactive module? |
Damn it, you are right... It's just too hard to review all the RESTEasy stuff in the Github UI... It's just too hard to get mixed up regarding the module that is affected... Now I know to pay much more attention. Would you like to update this PR with a commit that reverts #20271? |
Otherwise, I can do it. I just don't want to have the build broken again before the proper fix is in |
I though that was fine, because the SPI does not depend on resteasy-classic, and it also is very specific to Quarkus. So AFAICS, we could use the same SPI for both. |
Technically yeah, it's not a problem. But we really want to the two to be totally separate. |
Should we just have a common SPI module for stuff like this (where it does not actually depend on anything specific to one or the other)? |
Yeah, for things that are common, that makes sense. I'll looke into it after |
51a867a
to
16ec92c
Compare
I have added an SPI module just with this class as a starting point. |
This workflow status is outdated as a new workflow run has been triggered. Failing Jobs - Building 16ec92c
Full information is available in the Build summary check run. Failures⚙️ Gradle Tests - JDK 11 Windows #- Failing: integration-tests/gradle
📦 integration-tests/gradle✖
⚙️ JVM Tests - JDK 11 #- Failing: integration-tests/spring-web
📦 integration-tests/spring-web✖
⚙️ JVM Tests - JDK 11 Windows #- Failing: extensions/amazon-lambda/deployment integration-tests/spring-web
! Skipped: docs extensions/amazon-lambda-http/deployment extensions/amazon-lambda-rest/deployment and 6 more 📦 extensions/amazon-lambda/deployment✖
📦 integration-tests/spring-web✖
⚙️ JVM Tests - JDK 16 #- Failing: integration-tests/spring-web
📦 integration-tests/spring-web✖
⚙️ Native Tests - Spring #- Failing: integration-tests/spring-web
📦 integration-tests/spring-web✖
|
16ec92c
to
8edd6e2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the reason tests are still failing is an import that wasn't updated; see below.
...ent/src/main/java/io/quarkus/hibernate/validator/deployment/HibernateValidatorProcessor.java
Outdated
Show resolved
Hide resolved
...ent/src/main/java/io/quarkus/hibernate/validator/deployment/HibernateValidatorProcessor.java
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Damn that was fast.
8edd6e2
to
b742826
Compare
Failing Jobs - Building b742826
Full information is available in the Build summary check run. Failures⚙️ Gradle Tests - JDK 11 Windows #- Failing: integration-tests/gradle
📦 integration-tests/gradle✖
|
No description provided.