Bump gotest.tools/gotestsum from 1.12.3 to 1.13.0 in /internal/tools

[dependabot]

Bumps gotest.tools/gotestsum from 1.12.3 to 1.13.0.

Release notes

Sourced from gotest.tools/gotestsum's releases.

v1.13.0

What's Changed

• add --watch-clear flag to clear screen on rerun test by @​krhubert in gotestyourself/gotestsum#507
• Show correct version when installed via go install by @​devleejb in gotestyourself/gotestsum#520
• Add support for go test attributes by @​noBlubb in gotestyourself/gotestsum#522
• Bump github.com/fsnotify/fsnotify from 1.8.0 to 1.9.0 by @​dependabot[bot] in gotestyourself/gotestsum#486

New Contributors

• @​krhubert made their first contribution in gotestyourself/gotestsum#507
• @​devleejb made their first contribution in gotestyourself/gotestsum#520

Full Changelog: gotestyourself/gotestsum@v1.12.3...v1.12.4

Commits

• c4a0df2 Merge pull request #526 from gotestyourself/dependabot/go_modules/golang.org/...
• 53b29fa Merge pull request #525 from gotestyourself/dependabot/go_modules/golang.org/...
• 04f4268 Merge pull request #527 from dnephin/update-golangci-lint-v2
• 578cbcc Merge pull request #522 from noBlubb/feat/add-go-test-attribute-support
• 54d88a5 Bump golang.org/x/sync from 0.16.0 to 0.17.0
• 186bf04 Bump golang.org/x/term from 0.34.0 to 0.35.0
• 77d5f39 Update golangci-lint
• 1f1f8c3 Merge pull request #524 from gotestyourself/dependabot/go_modules/golang.org/...
• 67630d7 Fix lint
• bc4ff63 Update golangci-lint
• 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.

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: cd23f01f-64a8-43ea-b066-7de94b63ccf6

Baseline: 6341ab1
Comparison: 20d8a3e
Diff

Optimization Goals: ✅ Improvement(s) detected

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
✅	docker_containers_memory	memory utilization	-5.18	[-5.64, -4.71]	1	Logs

Experiments ignored for regressions

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

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
❌	docker_containers_cpu	% cpu utilization	+40.69	[+39.34, +42.04]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
❌	docker_containers_cpu	% cpu utilization	+40.69	[+39.34, +42.04]	1	Logs
➖	quality_gate_metrics_logs	memory utilization	+0.75	[+0.54, +0.97]	1	Logs bounds checks dashboard
➖	otlp_ingest_logs	memory utilization	+0.48	[+0.36, +0.60]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.39	[+0.35, +0.43]	1	Logs bounds checks dashboard
➖	ddot_metrics_sum_delta	memory utilization	+0.35	[+0.21, +0.49]	1	Logs
➖	ddot_logs	memory utilization	+0.35	[+0.29, +0.41]	1	Logs
➖	quality_gate_idle	memory utilization	+0.33	[+0.30, +0.37]	1	Logs bounds checks dashboard
➖	ddot_metrics_sum_cumulative	memory utilization	+0.29	[+0.17, +0.41]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	+0.09	[+0.03, +0.16]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.02	[-0.23, +0.26]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	-0.00	[-0.01, +0.01]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.04	[-0.65, +0.57]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.05	[-0.68, +0.59]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.06	[-0.60, +0.49]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.06	[-0.66, +0.54]	1	Logs
➖	ddot_metrics_sum_cumulativetodelta_exporter	memory utilization	-0.09	[-0.28, +0.11]	1	Logs
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	-0.11	[-0.16, -0.06]	1	Logs
➖	ddot_metrics	memory utilization	-0.19	[-0.36, -0.03]	1	Logs
➖	otlp_ingest_metrics	memory utilization	-0.30	[-0.43, -0.18]	1	Logs
➖	file_tree	memory utilization	-0.62	[-0.66, -0.58]	1	Logs
➖	quality_gate_logs	% cpu utilization	-3.60	[-6.34, -0.87]	1	Logs bounds checks dashboard
✅	docker_containers_memory	memory utilization	-5.18	[-5.64, -4.71]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	links
✅	docker_containers_cpu	simple_check_run	10/10
✅	docker_containers_memory	memory_usage	10/10
✅	docker_containers_memory	simple_check_run	10/10
✅	file_to_blackhole_0ms_latency	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10
✅	file_to_blackhole_100ms_latency	lost_bytes	10/10
✅	file_to_blackhole_100ms_latency	memory_usage	10/10
✅	file_to_blackhole_500ms_latency	lost_bytes	10/10
✅	file_to_blackhole_500ms_latency	memory_usage	10/10
✅	quality_gate_idle	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_logs	lost_bytes	10/10	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	lost_bytes	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	bounds checks dashboard

Explanation

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

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

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".

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

• quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.

[agent-platform-auto-pr]

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor 597d244

Successful checks

Info

	Quality gate	Delta	On disk size (MiB)	Delta	On wire size (MiB)
✅	agent_deb_amd64	$${0}$$	$${697.44}$$ < $${703.13}$$	$${+0.01}$$	$${175.51}$$ < $${178.38}$$
✅	agent_deb_amd64_fips	$${0}$$	$${691.93}$$ < $${697.61}$$	$${-0.04}$$	$${174.11}$$ < $${177.15}$$
✅	agent_heroku_amd64	$${0}$$	$${335.98}$$ < $${341.62}$$	$${+0}$$	$${88.95}$$ < $${91.52}$$
✅	agent_msi	$${0}$$	$${989.02}$$ < $${990.42}$$	$${0}$$	$${150.93}$$ < $${152.42}$$
✅	agent_rpm_amd64	$${0}$$	$${697.43}$$ < $${703.12}$$	$${-0}$$	$${177.83}$$ < $${180.53}$$
✅	agent_rpm_amd64_fips	$${0}$$	$${691.92}$$ < $${697.6}$$	$${+0.02}$$	$${176.25}$$ < $${178.87}$$
✅	agent_rpm_arm64	$${0}$$	$${683.51}$$ < $${689.82}$$	$${+0.01}$$	$${159.07}$$ < $${162.16}$$
✅	agent_rpm_arm64_fips	$${0}$$	$${679.03}$$ < $${685.08}$$	$${+0}$$	$${158.03}$$ < $${161.11}$$
✅	agent_suse_amd64	$${0}$$	$${697.43}$$ < $${703.12}$$	$${-0}$$	$${177.83}$$ < $${180.53}$$
✅	agent_suse_amd64_fips	$${0}$$	$${691.92}$$ < $${697.6}$$	$${+0.02}$$	$${176.25}$$ < $${178.87}$$
✅	agent_suse_arm64	$${0}$$	$${683.51}$$ < $${689.82}$$	$${+0.01}$$	$${159.07}$$ < $${162.16}$$
✅	agent_suse_arm64_fips	$${0}$$	$${679.03}$$ < $${685.08}$$	$${+0}$$	$${158.03}$$ < $${161.11}$$
✅	docker_agent_amd64	$${-0}$$	$${768.81}$$ < $${774.54}$$	$${+0}$$	$${263.29}$$ < $${266.46}$$
✅	docker_agent_arm64	$${-0}$$	$${778.84}$$ < $${785.2}$$	$${-0}$$	$${249.35}$$ < $${252.92}$$
✅	docker_agent_jmx_amd64	$${+0}$$	$${959.68}$$ < $${965.41}$$	$${-0}$$	$${331.91}$$ < $${335.08}$$
✅	docker_agent_jmx_arm64	$${0}$$	$${958.31}$$ < $${964.66}$$	$${-0}$$	$${313.96}$$ < $${317.54}$$
✅	docker_cluster_agent_amd64	$${0}$$	$${212.95}$$ < $${213.74}$$	$${+0}$$	$${72.24}$$ < $${73.2}$$
✅	docker_cluster_agent_arm64	$${-0}$$	$${228.86}$$ < $${229.68}$$	$${-0}$$	$${68.52}$$ < $${69.48}$$
✅	docker_cws_instrumentation_amd64	$${0}$$	$${7.06}$$ < $${7.12}$$	$${0}$$	$${2.95}$$ < $${3.29}$$
✅	docker_cws_instrumentation_arm64	$${0}$$	$${6.69}$$ < $${6.92}$$	$${+0}$$	$${2.7}$$ < $${3.07}$$
✅	docker_dogstatsd_amd64	$${0}$$	$${38.41}$$ < $${39.3}$$	$${-0}$$	$${14.84}$$ < $${15.76}$$
✅	docker_dogstatsd_arm64	$${0}$$	$${37.05}$$ < $${37.94}$$	$${+0}$$	$${14.28}$$ < $${14.83}$$
✅	dogstatsd_deb_amd64	$${0}$$	$${29.64}$$ < $${30.53}$$	$${+0}$$	$${7.82}$$ < $${8.75}$$
✅	dogstatsd_deb_arm64	$${0}$$	$${28.22}$$ < $${29.12}$$	$${-0}$$	$${6.77}$$ < $${7.71}$$
✅	dogstatsd_rpm_amd64	$${0}$$	$${29.64}$$ < $${30.53}$$	$${+0}$$	$${7.84}$$ < $${8.77}$$
✅	dogstatsd_suse_amd64	$${0}$$	$${29.64}$$ < $${30.53}$$	$${+0}$$	$${7.84}$$ < $${8.77}$$
✅	iot_agent_deb_amd64	$${0}$$	$${54.6}$$ < $${54.97}$$	$${+0}$$	$${13.65}$$ < $${14.45}$$
✅	iot_agent_deb_arm64	$${0}$$	$${51.88}$$ < $${51.9}$$	$${+0}$$	$${11.77}$$ < $${12.63}$$
✅	iot_agent_deb_armhf	$${0}$$	$${51.41}$$ < $${51.84}$$	$${+0}$$	$${11.85}$$ < $${12.74}$$
✅	iot_agent_rpm_amd64	$${0}$$	$${54.6}$$ < $${54.97}$$	$${+0}$$	$${13.66}$$ < $${14.47}$$
✅	iot_agent_suse_amd64	$${0}$$	$${54.6}$$ < $${54.97}$$	$${+0}$$	$${13.66}$$ < $${14.47}$$

[dd-octo-sts]

This pull request has been automatically marked as stale because it has not had activity in the past 15 days.

It will be closed in 30 days if no further activity occurs. If this pull request is still relevant, adding a comment or pushing new commits will keep it open. Also, you can always reopen the pull request if you missed the window.

Thank you for your contributions!