Debugger fix coverage#11807
Conversation
|
Hi! 👋 Thanks for your pull request! 🎉 To help us review it, please make sure to:
If you need help, please check our contributing guidelines. |
🟢 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. |
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 (330.977 µs) : 309, 353
. : milestone, 331,
basic (297.657 µs) : 291, 305
. : milestone, 298,
loop (8.987 ms) : 8982, 8993
. : milestone, 8987,
section candidate
noprobe (336.129 µs) : 303, 369
. : milestone, 336,
basic (297.424 µs) : 290, 305
. : milestone, 297,
loop (8.998 ms) : 8992, 9003
. : milestone, 8998,
|
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
The merge request has been interrupted because the build 1622620339817469906 took longer than expected. The current limit for the base branch 'master' is 120 minutes. |
fix coverage for - ExceptionProbeManager.ThrowableState - SpringHelper.ParserSpringVersion - SourceMapper - ConfigurationUpdater
0e0ca30 to
8e40b6c
Compare
|
🎯 Code Coverage (details) 🔗 Commit SHA: c28eb7f | Docs | Datadog PR Page | Give us feedback! |
JDK version or Spring version dependent
40e315f to
53a5014
Compare
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
This PR is rejected because it was updated |
enable Kotlin for all JDKs
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
What Does This Do
fix coverage for
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: [PROJ-IDENT]