Commit 0aafdb1
Fix AWS SDK timeout test flake
The "timeout and retry errors captured" test could record the AWS
timeout as several different exception types depending on where the
timeout was enforced (SDK wrapper vs underlying IO abort), and with
slightly different message text. The previous try/catch assertion
expected one specific (class, message) combination in each branch
and intermittently failed when neither matched.
Accept either an AmazonClientException (covers SdkClientException
and friends) or an IOException, with any String error.message. This
matches what the span actually records across the observed flake
variants without depending on a stable message string.
Remove the @flaky annotation since the assertion is now deterministic
under the observed failure modes.
Test-only change; no instrumentation behavior modified.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>1 parent a5138d1 commit 0aafdb1
1 file changed
Lines changed: 2 additions & 4 deletions
File tree
- dd-java-agent/instrumentation/aws-java/aws-java-sdk-1.11/src/test/groovy
Lines changed: 2 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
40 | 40 | | |
41 | 41 | | |
42 | 42 | | |
43 | | - | |
44 | 43 | | |
45 | 44 | | |
46 | 45 | | |
| |||
346 | 345 | | |
347 | 346 | | |
348 | 347 | | |
349 | | - | |
350 | 348 | | |
351 | 349 | | |
352 | 350 | | |
| |||
393 | 391 | | |
394 | 392 | | |
395 | 393 | | |
396 | | - | |
| 394 | + | |
397 | 395 | | |
398 | | - | |
| 396 | + | |
399 | 397 | | |
400 | 398 | | |
401 | 399 | | |
| |||
0 commit comments