-
Notifications
You must be signed in to change notification settings - Fork 283
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
Force test failure on unhandled instrumented exception #6546
Conversation
BenchmarksStartupParameters
See matching parameters
SummaryFound 0 performance improvements and 0 performance regressions! Performance is the same for 45 metrics, 9 unstable metrics. LoadParameters
See matching parameters
SummaryFound 1 performance improvements and 0 performance regressions! Performance is the same for 10 metrics, 15 unstable metrics.
Request duration reports for insecure-bankgantt
title insecure-bank - request duration [CI 0.99] : candidate=1.29.0-SNAPSHOT~678f89692b, baseline=1.29.0-SNAPSHOT~1557ad19cf
dateFormat X
axisFormat %s
section baseline
no_agent (369.181 µs) : 349, 390
. : milestone, 369,
iast (477.247 µs) : 457, 498
. : milestone, 477,
iast_FULL (538.229 µs) : 518, 559
. : milestone, 538,
iast_GLOBAL (512.219 µs) : 491, 534
. : milestone, 512,
iast_HARDCODED_SECRET_DISABLED (478.911 µs) : 458, 500
. : milestone, 479,
iast_INACTIVE (447.579 µs) : 427, 468
. : milestone, 448,
iast_TELEMETRY_OFF (471.307 µs) : 450, 492
. : milestone, 471,
tracing (433.351 µs) : 413, 453
. : milestone, 433,
section candidate
no_agent (364.505 µs) : 345, 384
. : milestone, 365,
iast (471.102 µs) : 450, 492
. : milestone, 471,
iast_FULL (540.612 µs) : 520, 561
. : milestone, 541,
iast_GLOBAL (504.375 µs) : 483, 525
. : milestone, 504,
iast_HARDCODED_SECRET_DISABLED (476.382 µs) : 455, 498
. : milestone, 476,
iast_INACTIVE (442.783 µs) : 422, 463
. : milestone, 443,
iast_TELEMETRY_OFF (472.201 µs) : 451, 493
. : milestone, 472,
tracing (453.434 µs) : 431, 476
. : milestone, 453,
Request duration reports for petclinicgantt
title petclinic - request duration [CI 0.99] : candidate=1.29.0-SNAPSHOT~678f89692b, baseline=1.29.0-SNAPSHOT~1557ad19cf
dateFormat X
axisFormat %s
section baseline
no_agent (1.353 ms) : 1334, 1372
. : milestone, 1353,
appsec (1.772 ms) : 1747, 1797
. : milestone, 1772,
iast (1.521 ms) : 1497, 1546
. : milestone, 1521,
profiling (1.596 ms) : 1570, 1622
. : milestone, 1596,
tracing (1.521 ms) : 1496, 1546
. : milestone, 1521,
section candidate
no_agent (1.359 ms) : 1340, 1378
. : milestone, 1359,
appsec (1.795 ms) : 1770, 1820
. : milestone, 1795,
iast (1.517 ms) : 1493, 1542
. : milestone, 1517,
profiling (1.528 ms) : 1502, 1554
. : milestone, 1528,
tracing (1.504 ms) : 1479, 1529
. : milestone, 1504,
|
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.
Nice! Especially like the idea to count these errors, as we can then expose that as a metric :)
fb5c464
to
3e7355a
Compare
...ent/agent-tooling/src/main/java/datadog/trace/agent/tooling/bytebuddy/ExceptionHandlers.java
Outdated
Show resolved
Hide resolved
@smola as discussed there are ASM tests failing because of "Interaction with TraceSegment after root span has already finished" Till today this error was triggered but the exception handler did not record the failure. Today is happening and the tests are failing. This check makes sense when strict trace writing is enabled. Now, I aligned it and disabled strict trace writing for grizzly tests that are showing those failures. A fixme is reminding that at long term we should probably fix that instrumentation |
50302aa
to
678f896
Compare
8800f3d
to
76ee2c7
Compare
What Does This Do
Motivation
Additional Notes
Jira ticket: [PROJ-IDENT]