-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
@QuarkusIntegrationTest with docker image fails on unable to create logfile #17565
Comments
So you essentially would like to be able to read the log file? |
The problem is that
If I create the second |
Can you upload a reproducer project? |
Ugh, while creating the minimal project, I I found the cause in one of our default parent poms which sets the working directory to
Which causes this issue, however, it would still be nice if these kind settings where supported, maybe by adding: |
Makes sense. Here it is: #17580 |
Create log file parent directories for @QuarkusIntegrationTest
Fixes: quarkusio#17565 (cherry picked from commit 9eb7b90)
Fixes: quarkusio#17565 (cherry picked from commit 9eb7b90)
When running an integration test with the new @QuarkusIntegrationTest annotation against a compiled docker image, it will redirect the output to a logfile which resides in a folder that does not exists. Only option to currently is to create the folder before the tests are run (using (static) initializer or QuarkusTestResourceLifecycleManager).
The log file is set here:
quarkus/test-framework/common/src/main/java/io/quarkus/test/common/DockerContainerLauncher.java
Line 93 in fdf16eb
The method
getLogFilePath
doesn't make much sense, since:quarkus/test-framework/common/src/main/java/io/quarkus/test/common/PropertyTestUtil.java
Line 33 in c2801d4
will always contain two parts:
target
and the value ofquarkus.log.file.path
which defauls toquarkus.log
.So, using default settings it will try to access the file
target/quarkus.log
, but the working directory is the target folder, so it actually tries to write totarget/target/quarkus.log
, which doesn't exists and fails.Also settings custom paths for
quarkus.log.file.path
gives an error becausetarget/
is prepended.The text was updated successfully, but these errors were encountered: