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

Support forkjoinpool plugin in JDK11 #656

Merged
merged 6 commits into from
Dec 18, 2023
Merged

Support forkjoinpool plugin in JDK11 #656

merged 6 commits into from
Dec 18, 2023

Conversation

786991884
Copy link
Contributor

@wu-sheng
Copy link
Member

wu-sheng commented Dec 7, 2023

You need to add the test scenario to run in JDK 11, otherwise, this is only a manual test

@wu-sheng wu-sheng added enhancement New feature or request plugin labels Dec 7, 2023
@wu-sheng
Copy link
Member

wu-sheng commented Dec 7, 2023

Also, you removed the pull request template, we need that, and you missed the update in the change log.

@wu-sheng
Copy link
Member

wu-sheng commented Dec 9, 2023

You need to add the test scenario to run in JDK 11, otherwise, this is only a manual test

This is still missed.

@wu-sheng
Copy link
Member

Why do you open a new test3 with so many cases?

strategy:
matrix:
case:
- jdk11-forkjoinpool-scenario
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need a new case? I think this is rt.jar(jdk level) change, even the codes are compiled as 1.8, the runtime method is still going to be forced to run in 11, right?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we not copy the test scenario, but directly write the existing test in jdk11. Was that failing before and running now?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, you are right. I will optimize it

@@ -33,6 +33,9 @@ public class ForkJoinWorkerQueueInstrumentation extends ClassInstanceMethodsEnha
private static final String FORK_JOIN_WORKER_QUEUE_CLASS = "java.util.concurrent.ForkJoinPool$WorkQueue";

private static final String FORK_JOIN_WORKER_QUEUE_RUN_TASK_METHOD = "runTask";

private static final String FORK_JOIN_WORKER_QUEUE_RUN_TASK_METHOD_JDK11 = "topLevelExec";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add comments about why there are two methods to intercept.

@wu-sheng
Copy link
Member

From test logs, your interceptor doesn't run as expected. Still, the old method existed and being intercepted.

@wu-sheng
Copy link
Member

Tests passed, could you check this? #656 (comment)

@wu-sheng
Copy link
Member

Is there any update here?

@wu-sheng
Copy link
Member

@786991884 Do you have any update?

@wu-sheng wu-sheng added the stale label Dec 18, 2023
@wu-sheng wu-sheng removed the stale label Dec 18, 2023
@wu-sheng wu-sheng added this to the 9.2.0 milestone Dec 18, 2023
@wu-sheng
Copy link
Member

@786991884 If you will be back, I hope this extra test can be removed by reusing the existing one.

I am going to merge this first because from what I saw, this fix is important.

@wu-sheng wu-sheng merged commit c5d62cb into apache:main Dec 18, 2023
186 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request plugin
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] api-jdk-forkjoinpool-plugin not effective in jdk11
2 participants