Skip to content

fix(contrib/aws/datadog-lambda): sort the logs to compare#4677

Merged
darccio merged 1 commit into
mainfrom
dario.castane/incident-52915/lambda-integration-tests
Apr 20, 2026
Merged

fix(contrib/aws/datadog-lambda): sort the logs to compare#4677
darccio merged 1 commit into
mainfrom
dario.castane/incident-52915/lambda-integration-tests

Conversation

@darccio

@darccio darccio commented Apr 20, 2026

Copy link
Copy Markdown
Member

What does this PR do?

This PR sorts the logs generated by contrib/aws/datadog-lambda-go/test/integration_tests/run_integration_tests.sh when running Lambda Integration tests.

Motivation

Avoid flakiness in the scheduled runs.

Reviewer's Checklist

  • Changed code has unit tests for its functionality at or near 100% coverage.
  • System-Tests covering this feature have been added and enabled with the va.b.c-dev version tag.
  • There is a benchmark for any new code, or changes to existing code.
  • If this interacts with the agent in a new way, a system test has been added.
  • New code is free of linting errors. You can check this by running make lint locally.
  • New code doesn't break existing tests. You can check this by running make test locally.
  • Add an appropriate team label so this PR gets put in the right place for the release notes.
  • All generated files are up to date. You can check this by running make generate locally.
  • Non-trivial go.mod changes, e.g. adding new modules, are reviewed by @DataDog/dd-trace-go-guild. Make sure all nested modules are up to date by running make fix-modules locally.

Unsure? Have a question? Request a review!

@github-actions github-actions Bot added the apm:ecosystem contrib/* related feature requests or bugs label Apr 20, 2026
@datadog-datadog-prod-us1-2

datadog-datadog-prod-us1-2 Bot commented Apr 20, 2026 •
edited by datadog-official Bot
Loading

Copy link
Copy Markdown

Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 60.89% (+4.16%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: cf21634 | Docs | Datadog PR Page | Give us feedback!

@codecov

codecov Bot commented Apr 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 61.51%. Comparing base (d6dc3b9) to head (cf21634).

Additional details and impacted files

see 445 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@pr-commenter

pr-commenter Bot commented Apr 20, 2026

Copy link
Copy Markdown

Benchmarks

Benchmark execution time: 2026-04-20 12:03:32

Comparing candidate commit cf21634 in PR branch dario.castane/incident-52915/lambda-integration-tests with baseline commit d6dc3b9 in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 269 metrics, 9 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

  • 🟩 = significantly better candidate vs. baseline
  • 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

@darccio
darccio marked this pull request as ready for review April 20, 2026 12:52
@darccio
darccio requested review from a team as code owners April 20, 2026 12:52
@darccio
darccio requested a review from duncanista April 20, 2026 12:52
@darccio
darccio merged commit 21bb70d into main Apr 20, 2026
189 checks passed
@darccio
darccio deleted the dario.castane/incident-52915/lambda-integration-tests branch April 20, 2026 13:05
@joeyzhao2018 joeyzhao2018 mentioned this pull request Apr 20, 2026
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@duncanista duncanista duncanista approved these changes

Assignees

No one assigned

Labels

apm:ecosystem contrib/* related feature requests or bugs

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@darccio @duncanista