Fix Spring MethodParameters detection#11647
Conversation
Avoid throwing an exception if Spring is not found in loaded classes Introduced an enum for reporting back result state and use UNKNOWN to fallback to another detection method.
This comment has been minimized.
This comment has been minimized.
Debugger benchmarksParameters
See matching parameters
SummaryFound 0 performance improvements and 0 performance regressions! Performance is the same for 10 metrics, 5 unstable metrics. See unchanged results
Request duration reports for reportsgantt
title reports - request duration [CI 0.99] : candidate=None, baseline=None
dateFormat X
axisFormat %s
section baseline
noprobe (333.602 µs) : 310, 357
. : milestone, 334,
basic (296.058 µs) : 290, 302
. : milestone, 296,
loop (8.977 ms) : 8972, 8983
. : milestone, 8977,
section candidate
noprobe (335.57 µs) : 306, 365
. : milestone, 336,
basic (296.561 µs) : 291, 302
. : milestone, 297,
loop (8.984 ms) : 8979, 8989
. : milestone, 8984,
|
🟢 Java Benchmark SLOs — All performance SLOs passed
PR vs. master results
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
What Does This Do
Avoid throwing an exception if Spring is not found in loaded classes Introduced an enum for reporting back result state and use UNKNOWN to fallback to another detection method.
Motivation
Additional Notes
Contributor Checklist
type:and (comp:orinst:) labels in addition to any other useful labelsclose,fix, or any linking keywords when referencing an issueUse
solvesinstead, and assign the PR milestone to the issue/merge. You can also:/merge --commit-message "..."/merge -c/merge -f --reason "reason"; please use this judiciously, as some checks do not run at the PR-level (note: the PR still needs to be mergeable, this will only skip the pre-merge build)Jira ticket: DEBUG-5725