test

[gnufede]

Checklist

• PR author has checked that all the criteria below are met
• The PR description includes an overview of the change
• The PR description articulates the motivation for the change
• The change includes tests OR the PR description describes a testing strategy
• The PR description notes risks associated with the change, if any
• Newly-added code is easy to change
• The change follows the library release note guidelines
• The change includes or references documentation updates if necessary
• Backport labels are set (if applicable)

Reviewer Checklist

• Reviewer has checked that all the criteria below are met
• Title is accurate
• All changes are related to the pull request's stated goal
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Newly-added code is easy to change
• Release note makes sense to a user of the library
• If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
• Backport labels are set in a manner that is consistent with the release branch maintenance policy

[github-actions]

CODEOWNERS have been resolved as:

ddtrace/appsec/_iast/_ast/ast_patching.py                               @DataDog/asm-python

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: gnufede/aws-payload-tagging
Commit report: de1fe93
Test service: dd-trace-py

✅ 0 Failed, 595 Passed, 691 Skipped, 18m 47.85s Total duration (18m 1.9s time saved)

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-11-12 16:17:29

Comparing candidate commit dcf85c1 in PR branch gnufede/aws-payload-tagging with baseline commit 0b97536 in branch steven/aws-payload-tagging.

Found 1 performance improvements and 0 performance regressions! Performance is the same for 387 metrics, 2 unstable metrics.

scenario:iast_aspects-ospathnormcase_aspect

• 🟩 execution_time [-225.982ns; -201.480ns] or [-8.501%; -7.579%]