-
Notifications
You must be signed in to change notification settings - Fork 189
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
Optaplanner native integration tests fail with Quarkus 1.12 #2205
Comments
@jamesnetherton Can you assign this to me ? I'll give a look at it. |
This is not occurring anymore, is it? |
Optaplanner solver is way too slow in Native mode compared to JVM. I don't remember how was the difference between native and JVM before the recent updates. I'll need to check if our example is still up-to-date, or if it's a normal behaviour from Optaplanner |
Is this still occurring? Can't we close this issue? |
I think we can close this one |
Hi @ppalaga @zbendhiba , Just FYI, the OptaplannerIT still consistently fails on my machine(it's disabled in CI now). Thanks! |
Yes, the optaplanner is passing for me in native mode. |
Thanks @ppalaga for the confirmation! |
/CC @zbendhiba
This has popped up a few times on the quarkus-master branch build. Not sure if its a genuine issue caused by Quarkus 1.12 or just a flaky test.
The text was updated successfully, but these errors were encountered: