Bump github.com/aws/aws-sdk-go-v2/service/eks from 1.35.1 to 1.39.0 in /test/new-e2e

[dependabot[bot]]

trafficstars

Bumps github.com/aws/aws-sdk-go-v2/service/eks from 1.35.1 to 1.39.0.

Commits

• 807c921 Release 2023-09-20
• 39b991d Regenerated Clients
• b1d6daf Update endpoints model
• 5771d22 Update API model
• 7143703 Release 2023-09-19
• 1803c87 Regenerated Clients
• 228b865 Update endpoints model
• f416d66 Update API model
• f0b396e Release 2023-09-18
• 5389625 Regenerated Clients
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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)

[pr-commenter[bot]]

Bloop Bleep... Dogbot Here

Regression Detector Results

Run ID: 94882d2f-302d-4c9a-81f5-de234b03da13 Baseline: e45cfd9d3f80dbd35ac5cf838ad27c78c3006b6d Comparison: 7615772605b9b3c49d0efaa0264be45efbbe18fd

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

Experiments with missing or malformed data

• basic_py_check

Usually, this warning means that there is no usable optimization goal data for that experiment, which could be a result of misconfiguration.

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.

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	file_to_blackhole	% cpu utilization	+0.20	[-6.41, +6.82]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	process_agent_real_time_mode	memory utilization	+1.12	[+1.07, +1.16]
➖	idle	memory utilization	+0.66	[+0.62, +0.71]
➖	process_agent_standard_check_with_stats	memory utilization	+0.20	[+0.18, +0.23]
➖	file_to_blackhole	% cpu utilization	+0.20	[-6.41, +6.82]
➖	tcp_syslog_to_blackhole	ingress throughput	+0.05	[-0.01, +0.11]
➖	trace_agent_json	ingress throughput	+0.01	[-0.02, +0.03]
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.00, +0.00]
➖	uds_dogstatsd_to_api	ingress throughput	-0.00	[-0.00, +0.00]
➖	trace_agent_msgpack	ingress throughput	-0.01	[-0.02, -0.01]
➖	process_agent_standard_check	memory utilization	-0.21	[-0.26, -0.16]
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-0.21	[-1.63, +1.21]
➖	file_tree	memory utilization	-0.59	[-0.71, -0.47]
➖	otel_to_otel_logs	ingress throughput	-0.75	[-1.39, -0.11]

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