Bump github.com/aws/aws-sdk-go-v2/service/ec2 from 1.164.2 to 1.165.1 in /test/new-e2e

[dependabot]

Bumps github.com/aws/aws-sdk-go-v2/service/ec2 from 1.164.2 to 1.165.1.

Commits

• 2d43b81 Release 2024-06-19
• 812bc72 Regenerated Clients
• 12e2648 Update endpoints model
• 5df426a Update API model
• 78777b6 add implicit global region to internal partition metadata (#2688)
• 077df5d Release 2024-06-18
• 3320b13 Regenerated Clients
• 1315201 Update API model
• 8dddc9c add SDK-specific feature tracking (#2682)
• See full diff 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]

Regression Detector

Regression Detector Results

Run ID: 978665cf-3bb7-4a9e-9183-2cdc787ece6f Metrics dashboard Target profiles

Baseline: eccdad0
Comparison: 16b579c

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	+3.12	[-1.78, +8.01]	Logs
➖	basic_py_check	% cpu utilization	+1.80	[-0.81, +4.40]	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+0.53	[-0.38, +1.44]	Logs
➖	idle	memory utilization	+0.06	[+0.03, +0.10]	Logs
➖	otel_to_otel_logs	ingress throughput	+0.06	[-0.75, +0.87]	Logs
➖	file_tree	memory utilization	+0.04	[-0.05, +0.13]	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.01, +0.01]	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.00	[-0.00, +0.00]	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-0.39	[-13.34, +12.56]	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".

[pducolin]

/merge

[dd-devflow]

🚂 MergeQueue: pull request added to the queue

The median merge time in main is 24m.

Use /merge -c to cancel this operation!

[dd-devflow]

❌ MergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for 944923d

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected before the end of the pipeline.

You should have a look at the pipeline, wait for the build to finish and investigate the failures.
When you are ready, re-add your pull request to the queue!

⚠️ Do NOT retry failed jobs directly.

They were executed on a temporary branch created by the merge queue. If you retry them, they are going to fail because the branch no longer exists.

Details

List of failed jobs:

• go_mod_tidy_check

Go to failed Gitlab pipeline.

If you need support, contact us on Slack #devflow with those details!

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.