Skip to content
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

Merged
merged 1 commit into from
Sep 24, 2021
Merged

Conversation

stuartwdouglas
Copy link
Member

No description provided.

@quarkus-bot quarkus-bot bot added area/hibernate-validator Hibernate Validator area/rest area/spring Issues relating to the Spring integration labels Sep 21, 2021
@quarkus-bot
Copy link

quarkus-bot bot commented Sep 21, 2021

This workflow status is outdated as a new workflow run has been triggered.

Failing Jobs - Building 51a867a

Status Name Step Failures Logs Raw logs
Gradle Tests - JDK 11 Windows Build Failures Logs Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ Gradle Tests - JDK 11 Windows #

- Failing: integration-tests/gradle 

📦 integration-tests/gradle

io.quarkus.gradle.devmode.MultiModuleIncludedBuildTest.main line 24 - More details - Source on GitHub

java.lang.AssertionError: 

Expecting actual:

@geoand
Copy link
Contributor

geoand commented Sep 21, 2021

Was this intended to fix the SpringControllerTest.testInvalidJsonInputAndResult failure?

Asking because it was fixed with #20271

@stuartwdouglas
Copy link
Member Author

I did not notice that, but do we really want to be adding a resteasy-classic SPI artifact to a resteasy-reactive module?

@geoand
Copy link
Contributor

geoand commented Sep 21, 2021

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?

@geoand
Copy link
Contributor

geoand commented Sep 21, 2021

Otherwise, I can do it. I just don't want to have the build broken again before the proper fix is in

@yrodiere
Copy link
Member

I did not notice that, but do we really want to be adding a resteasy-classic SPI artifact to a resteasy-reactive module?

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.

@geoand
Copy link
Contributor

geoand commented Sep 21, 2021

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.

@stuartwdouglas
Copy link
Member Author

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

@geoand
Copy link
Contributor

geoand commented Sep 21, 2021

Yeah, for things that are common, that makes sense.

I'll looke into it after 2.3.0.CR1 is out.

@quarkus-bot quarkus-bot bot added the area/dependencies Pull requests that update a dependency file label Sep 22, 2021
@stuartwdouglas
Copy link
Member Author

I have added an SPI module just with this class as a starting point.

@quarkus-bot
Copy link

quarkus-bot bot commented Sep 22, 2021

This workflow status is outdated as a new workflow run has been triggered.

Failing Jobs - Building 16ec92c

Status Name Step Failures Logs Raw logs
Gradle Tests - JDK 11 Windows Build Failures Logs Raw logs
JVM Tests - JDK 11 Build Failures Logs Raw logs
JVM Tests - JDK 11 Windows Build Failures Logs Raw logs
JVM Tests - JDK 16 Build Failures Logs Raw logs
Native Tests - Spring Build Failures Logs Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ Gradle Tests - JDK 11 Windows #

- Failing: integration-tests/gradle 

📦 integration-tests/gradle

io.quarkus.gradle.devmode.MultiModuleIncludedBuildTest.main line 24 - More details - Source on GitHub

java.lang.AssertionError: 

Expecting actual:

⚙️ JVM Tests - JDK 11 #

- Failing: integration-tests/spring-web 

📦 integration-tests/spring-web

io.quarkus.it.spring.web.SpringControllerTest.testInvalidJsonInputAndResult line 37 - More details - Source on GitHub

java.lang.AssertionError: 
1 expectation failed.
Expected status code <400> but was <500>.

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

io.quarkus.amazon.lambda.deployment.testing.LambdaDevServicesContinuousTestingTestCase.testLambda line 41 - More details - Source on GitHub

org.opentest4j.AssertionFailedError: expected: <0> but was: <1>
	at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:55)
	at org.junit.jupiter.api.AssertionUtils.failNotEqual(AssertionUtils.java:62)

📦 integration-tests/spring-web

io.quarkus.it.spring.web.SpringControllerTest.testInvalidJsonInputAndResult line 37 - More details - Source on GitHub

java.lang.AssertionError: 
1 expectation failed.
Expected status code <400> but was <500>.

⚙️ JVM Tests - JDK 16 #

- Failing: integration-tests/spring-web 

📦 integration-tests/spring-web

io.quarkus.it.spring.web.SpringControllerTest.testInvalidJsonInputAndResult line 37 - More details - Source on GitHub

java.lang.AssertionError: 
1 expectation failed.
Expected status code <400> but was <500>.

⚙️ Native Tests - Spring #

- Failing: integration-tests/spring-web 

📦 integration-tests/spring-web

io.quarkus.it.spring.web.SpringControllerIT.testInvalidJsonInputAndResult - More details - Source on GitHub

java.lang.AssertionError: 
1 expectation failed.
Expected status code <400> but was <500>.

Copy link
Member

@yrodiere yrodiere left a 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.

Copy link
Member

@yrodiere yrodiere left a 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.

@quarkus-bot
Copy link

quarkus-bot bot commented Sep 22, 2021

Failing Jobs - Building b742826

Status Name Step Failures Logs Raw logs
Gradle Tests - JDK 11 Windows Build Failures Logs Raw logs
✔️ JVM Tests - JDK 11
JVM Tests - JDK 11 Windows Upload gc.log ⚠️ Check → Logs Raw logs
JVM Tests - JDK 16 Build ⚠️ Check → Logs Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ Gradle Tests - JDK 11 Windows #

- Failing: integration-tests/gradle 

📦 integration-tests/gradle

io.quarkus.gradle.devmode.MultiModuleIncludedBuildTest.main line 24 - More details - Source on GitHub

java.lang.AssertionError: 

Expecting actual:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dependencies Pull requests that update a dependency file area/hibernate-validator Hibernate Validator area/rest area/spring Issues relating to the Spring integration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants