Bump github.com/aws/aws-sdk-go-v2/service/ssm from 1.44.1 to 1.49.4 in /test/new-e2e

[dependabot]

Bumps github.com/aws/aws-sdk-go-v2/service/ssm from 1.44.1 to 1.49.4.

Commits

• 427c682 Release 2024-03-18
• 93e06ff Regenerated Clients
• 58be623 Update endpoints model
• 9927740 Update API model
• e5b7766 add ratelimit.None (#2562)
• 10c4487 Release 2024-03-15
• db0b1ab Regenerated Clients
• 92c0060 Update endpoints model
• e5bb86e Update API model
• 49b368e Release 2024-03-14
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[pr-commenter]

Test changes on VM

Use this command from test-infra-definitions to manually test this PR changes on a VM:

inv create-vm --pipeline-id=30546621 --os-family=ubuntu

[pr-commenter]

Regression Detector

Regression Detector Results

Run ID: 53526ab5-db68-4bae-b157-a2090f2227f6 Metrics dashboard Target profiles

Baseline: 6a6c459
Comparison: dd1e663

Performance changes are noted in the perf column of each table:

• ✅ = significantly better comparison variant performance
• ❌ = significantly worse comparison variant performance
• ➖ = no significant change in performance

No significant changes in experiment optimization goals

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	links
➖	pycheck_1000_100byte_tags	% cpu utilization	+0.95	[-3.89, +5.80]	Logs
➖	otel_to_otel_logs	ingress throughput	+0.59	[-0.23, +1.41]	Logs
➖	basic_py_check	% cpu utilization	+0.42	[-2.28, +3.12]	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.00, +0.00]	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.01, +0.01]	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-0.03	[-0.92, +0.86]	Logs
➖	idle	memory utilization	-0.10	[-0.13, -0.06]	Logs
➖	file_tree	memory utilization	-0.57	[-0.62, -0.53]	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-1.43	[-14.18, +11.32]	Logs

Explanation

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

3. Its configuration does not mark it "erratic".

[paulcacheux]

@dependabot rebase