-
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
Random test port stopped working in 1.6.0.Final #10477
Comments
Indeed I can reproduce when prefixing with |
FWIW: |
Thanks for the workaround(s). It would be nice if someone explained what is happening and why it is behaving differently in 1.6.0.Final. If it is a desired behavior (and not a bug), it could possibly be added to the migration guide? |
It's definitely a bug, I'll need to check it out |
@radcortez I think this is another incarnation of #9184. Now this might actually be the correct behavior from a config point of view - if you think it is, I will just make a small change to restore this specific test behavior |
#10488 fixes the problem for the tests |
@geoand if we follow the rule where a profile property always override a main property no matter the source priority, then yes, this is the correct behaviour. I'm wondering why in this particular case it was not following that rule. I also guess that this is one of the cases where @dmlloyd pointed out that once you set a profile property, there is no way to override it in a higher ordinal source, unless you override the profile property itself. |
Ensure that %test.quarkus.http.test-port works properly
I just realized that this is also broken for devmode via system property. Does that make sense? |
Meaning? |
"%dev":
quarkus:
http:
port: 2081 calling devmode: will use 2081 instead of a random port. I'll create a separate issue. Edit: #10570 |
Thanks |
Describe the bug
Configuring
%test.quarkus.http.test-port=0
makes Quarkus start on a free port.After 1.6.0.Final, tests fail with
java.lang.IllegalArgumentException: Port must be greater than 0
.Stacktrace
Expected behavior
The generated port should be propegated to rest-assured correclty.
To Reproduce
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: