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

Native test fails if quarkus.package.output-directory is configured differently #28131

Closed
stephan-strate opened this issue Sep 21, 2022 · 0 comments · Fixed by #28165
Closed
Assignees
Labels
area/testing kind/bug Something isn't working
Milestone

Comments

@stephan-strate
Copy link
Contributor

Describe the bug

If you leave the property native.image.path empty, the path is guessed by the system. Though it is always guessed in the default output location. If the quarkus.package.output-directory is changed (for example in the context of a ci pipeline), the native image can not be found.

======================================================================================
  native.image.path was not set, making a guess for the correct path of native image
  guessed path: /<path>/target/<name>-runner
======================================================================================

Expected behavior

If native.image.path is not defined and quarkus.package.output-directory is defined to output to a non-default directory. Then native.image.path should be guessed inside of the defined quarkus.package.output-directory.

Actual behavior

The native.image.path is always guessed in the default output location.

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

2.12.3.Final

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

@stephan-strate stephan-strate added the kind/bug Something isn't working label Sep 21, 2022
@geoand geoand self-assigned this Sep 23, 2022
geoand added a commit to geoand/quarkus that referenced this issue Sep 23, 2022
gsmet added a commit that referenced this issue Sep 26, 2022
Take quarkus.package.output-directory into account when launching native tests
@quarkus-bot quarkus-bot bot added this to the 2.14 - main milestone Sep 26, 2022
@gsmet gsmet modified the milestones: 2.14 - main, 2.13.1.Final Sep 30, 2022
gsmet pushed a commit to gsmet/quarkus that referenced this issue Oct 3, 2022
igorregis pushed a commit to igorregis/quarkus that referenced this issue Oct 16, 2022
igorregis pushed a commit to igorregis/quarkus that referenced this issue Oct 16, 2022
igorregis pushed a commit to igorregis/quarkus that referenced this issue Oct 16, 2022
igorregis pushed a commit to igorregis/quarkus that referenced this issue Oct 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants