Tests using @QuarkusIntegrationTest with @TestProfile fails after 3.16 upgrade from 3.15
#44764
Labels
Comments
|
/cc @geoand (kotlin,testing) |
|
Can you give |
geoand
added
triage/needs-feedback
|
If you mean the This is the stdout from running the |
|
Thanks for checking |
|
I'm curious how you created and 3.16 version. Mind including that in the reproducer? Thanks |
|
Sorry, the above text was just my subjective analysis of what would be happening. It creates it runs the QuarkusTestResource, Quarkus Application, QuarkusTestResource will inject into the test instance, then call the actual test 😅 In comparison, 3.15.2 Here is another version of the reproducer with the very contrived logging I've added. With the integration tests logging it prints several times the start() & stop() messages, incrementing the counter, in the end of the test start & stop 15 times (so the lambda mock server) This is the logging of the 3.15.2 3.17.0 |
|
Thanks a lot. I tried this but I'm having a really hard time debugging this. Thanks again! |
|
Sure, not familiar with Maven but I will give a try. Sorry this haven't been straight forward reproduce. I will try with Gradle without lambda first to see if relates to it. |
|
Thank you for your help! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
After upgrading to the latest version 3.16.4, the integration tests using
@TestProfilefail to run.I've included an reproducer for this and will now refer to to it when explaining the issue.
While on 3.15.2
While on 3.16.4
On 3.16.4 the test fails because the "DynamoClient" at the outer test by the
QuarkusTestResourceLifecycleManageris from a different lifecycle that has already been stopped.After running the tests on 3.16, searching for the application start log message
code-with-quarkus 1.0.0-SNAPSHOT nativeon the junit standard out logs, I can count 13 times. On the 3.15, I can find only 2 start log messages.Originally my issue was
Tests using @QuarkusIntegrationTest with @TestProfile take considerably longer time to execute.As example, on real production project 1 minutes 20 seconds run with 3.15, upgrading to 3.16 to lead the execution taking 16 minutes.
While investigating the issue seems that for each test, the Quarkus application starts & stop, extending the runtime for each. But when writing the issue reproduction test, I've modified a bit the test structure, leading to the failure above failure. Still I believe that the root cause is the same.
Expected behavior
The expected behavior is that the tests behave the same as 3.15.2, one application for the test class (since the test profile is the same).
Actual behavior
The current behavior is the test failing to run.
How to Reproduce?
I've attached a reproducer, running
quarkusIntTestwill result into the described issue.quarkus-kotlin-lambda-native-test.tar.gz
Output of
uname -aorverLinux cachyos-x8664 6.12.0-1-cachyos-autofdo SMP PREEMPT_DYNAMIC Mon, 18 Nov 2024 15:41:14 +0000 x86_64 GNU/Linux
Output of
java -versionOpenJDK 64-Bit Server VM GraalVM CE 23+37.1 (build 23+37-jvmci-b01, mixed mode, sharing)
Quarkus version or git rev
3.16.4
Build tool (ie. output of
mvnw --versionorgradlew --version)Gradle 8.9
Additional information
No response
The text was updated successfully, but these errors were encountered: