-
Notifications
You must be signed in to change notification settings - Fork 542
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
Change default debug options to not use legacy options #307
Conversation
Have you checked this change on Java 1.7 projects too? |
I haven't tested it in Java 1.7 yet. |
We have to make sure it is as you say, otherwise the Jenkins build would fail on old Java. |
@Thihup |
@Tibor17 I don't think so. Unfortunately, I don't have an extensive collection of projects with JaCoCo to test, but where I tested it worked fine. Hotspot: https://github.com/openjdk/jdk/blob/master/src/hotspot/share/runtime/arguments.cpp#L2878 Do you have something in mind that we should try? |
Yes, please check it out additionally with jacoco. |
Side note: for java 11, localhost:5005 is a saner default which works on java 8 (think 6 but didnt test), would be great to handle it too. |
@rmannibucau Sure. I didn't change to localhost:5005 because it changes the current behavior in JDK <= 8. I don't know if someone connects remotely during debug. If it OK to change I can change right away. @Tibor17 I've tested and it looks fine |
@Thihup thx |
@Thihup yep but 0.0.0.0:5005 is unsafe and not a good default anyway so guess it is better (if moving to current config as this issue is about) to fix that too properly. Worse case it is still configurable as before. |
@rmannibucau @Tibor17 I've changed to localhost:5005, however, some tests have failed and I couldn't understand why. |
The GH workflows are really crappy. After the MSC has taken it, this CI is unreliable. |
Is there something else I should do? |
@Thihup |
Using the -Xdebug -Xnoagent -Djava.compiler=NONE causes the OpenJ9 JVM to run the tests in interpreted mode, thus running them VERY slowly. In Hotspot JVM these options are ignored.
Done |
What did you change 2 hours ago? |
I've just rebased to the latest remote |
ok, i have created the Jira ticket SUREFIRE-1858. |
@Thihup Thx for contributing! |
Using the -Xdebug -Xnoagent -Djava.compiler=NONE causes the OpenJ9 JVM
to run the tests in interpreted mode, thus running them VERY slowly.
In Hotspot JVM these options are ignored.