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

Added JMH to be also built by code-tools #1021

Merged
merged 4 commits into from
May 28, 2024

Conversation

judovana
Copy link
Contributor

JMH is another code-tools openjdk project which release pretty randomly.
JMH suite itslef is engine to run benchamrks, and reelased versions are apearing in maven repos (similarly as jcstress).
JMH samples can be used as pretty good testsuite when reduced to run minimal iterations.

Generally spoken the build of TIP is heavily missed world wide.

Copy link

Thank you for creating a pull request!

Please check out the information below if you have not made a pull request here before (or if you need a reminder how things work).

Code Quality and Contributing Guidelines

If you have not done so already, please familiarise yourself with our Contributing Guidelines and Code Of Conduct, even if you have contributed before.

Tests

Github actions will run a set of jobs against your PR that will lint and unit test your changes. Keep an eye out for the results from these on the latest commit you submitted. For more information, please see our testing documentation.

In order to run the advanced pipeline tests (executing a set of mock pipelines), it requires an admin to post run tests on this PR.
If you are not an admin, please ask for one's attention in #infrastructure on Slack or ping one here.
To run full set of tests, use "run tests"; a subset of tests on specific jdk version, use "run tests quick 11,21"

@karianna
Copy link
Contributor

Is this actually required. Aleksey regularly releases this upstream

@judovana
Copy link
Contributor Author

Is this actually required. Aleksey regularly releases this upstream

I wish it is not requored:(

https://github.com/openjdk/jmh/tags - year ago
followed by https://github.com/openjdk/jmh/tags

But true - latest released is brobably not necessary. only tip.

@judovana
Copy link
Contributor Author

judovana commented May 2, 2024

Actually one reason to build both master and latest released - if the build of tip fails, it may behard to say it it is jdk or jmh who isguilty. If fails latest released, then it is most likely jdk.

@gdams
Copy link
Member

gdams commented May 3, 2024

ping @shipilev to see whether he does plan to continue building this or not

@sophia-guo
Copy link
Contributor

Is this still in progress as jenkinsfile also need to update if we'd like to build here?

@judovana
Copy link
Contributor Author

Is this still in progress as jenkinsfile also need to update if we'd like to build here?

Nope. sorry. I forget about it.

@judovana
Copy link
Contributor Author

@karianna @gdams Where shipilev.net is reliable build system, it is still private machine. However adoptium is trusted provider. Even the jmh on maven repos is till build on someones lcoalhost. Thus saying, we should be building JMH. Both latest release, and tip. in addition, tip is nowehre esle to be found

@shipilev
Copy link

The overwhemling majority of users consume JMH through Maven Central releases. So, unless you are planning to publish SNAPSHOT versions somewhere, I see no particular value in building JMH separately in Adoptium. I see no particular cost for it either, so it is your choice, really.

@judovana
Copy link
Contributor Author

tyvm!

@smlambert smlambert merged commit ffea6e6 into adoptium:master May 28, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants