-
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
BasicKotlinApplicationModuleDevModeTest times out if run first with clean caches #33890
Comments
/cc @evanchooly (kotlin), @geoand (kotlin), @gwenneg (cache) |
Any chance you have the logs of the failing application? |
Is this what you're looking for? This is from the very start of the tests to the end of the first test, which is the one that failed. Edit: that log was from an earlier failure from a known Gradle + Kotlin cache corruption issue. Let me look again. |
Here we are. This one is the one. |
I was hoping for the the application logs that would might be able to tell us what's going on. In any case, I kinda doubt we'll be able to get to be the botton of this without it occuring in our CI. If you do however a timeout related fix, we can probably accept it. |
Are you unable to reproduce it with the steps I gave in the issue? |
I am going to close this as won't fix for the time being since it doesn't really impact our CI and fixing it properly is probably more effort than it's worth |
Describe the bug
A clean .m2 and .gradle, followed by running the
io.quarkus.gradle.devmode.BasicKotlinApplicationModuleDevModeTest
Gradle integration test first, causes a timeout:This appears to be because the Kotlin dependencies take a proper age to download and populate the cache, which triggers this failure.
Even if the caches are populated, in my environment this test takes 70s~ to run which is of course 10s longer than the timeout in
integration-tests/gradle/src/test/java/io/quarkus/gradle/devmode/QuarkusDevGradleTestBase.java
😆I set the timeout to 10 minutes and the issue disappeared. (For me, caches took around 6-7m to populate.) A proper fix probably involves making sure that the tests' dependencies are somehow preloaded before running the actual test? I'm not sure.
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
./mvnw -f devtools/gradle/ install && ./mvnw -f integration-tests/gradle/ install -Dtest=BasicKotlinApplicationModuleDevModeTest
in the Quarkus repoOutput of
uname -a
orver
Linux jskillin-ubuntu-dev 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Output of
java -version
openjdk version "11.0.19" 2023-04-18 OpenJDK Runtime Environment (build 11.0.19+7-post-Ubuntu-0ubuntu123.04) OpenJDK 64-Bit Server VM (build 11.0.19+7-post-Ubuntu-0ubuntu123.04, mixed mode, sharing)
GraalVM version (if different from Java)
No response
Quarkus version or git rev
3.1.0.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)Gradle 8.1.1
Additional information
No response
The text was updated successfully, but these errors were encountered: