-
Notifications
You must be signed in to change notification settings - Fork 15
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
[23.0] Add JFR threshold checking before event emission #575
[23.0] Add JFR threshold checking before event emission #575
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@roberttoyonaga please use git cherry-pick -x
for the backports, so that we can map each commit to the one it is being backported from.
I also see some changes not being backported, e.g. oracle@d4a8436#diff-2b7c6208cd16f550c9422b6a4a25cabbb98034543abee1262f531edc253faa02
212e840
to
a4b52d1
Compare
@roberttoyonaga now that #577 is merged could you please change the build type in the mandrel.yml workflow to You can do so by adding the following line below
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, once the CI is happy it's OK to merge
CI failures will be fixed with quarkusio/quarkus#36058, not related with this PR. |
Summary
This PR backports threshold checking from 23.1 to 23.0. Specified duration thresholds will be checked before emitting events wherever thresholds are supported.
Original PR: oracle#6964
Oracle internal PR: oracle#7066