-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Bump github.com/samber/lo from 1.49.1 to 1.51.0 in /test/new-e2e #37993
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Bump github.com/samber/lo from 1.49.1 to 1.51.0 in /test/new-e2e #37993
Conversation
Bumps [github.com/samber/lo](https://github.com/samber/lo) from 1.49.1 to 1.51.0. - [Release notes](https://github.com/samber/lo/releases) - [Commits](samber/lo@v1.49.1...v1.51.0) --- updated-dependencies: - dependency-name: github.com/samber/lo dependency-version: 1.51.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
This commit was created from the local commit with hash 12b7f9f5579908b0840e32a3936f62b72b56d511.
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: e7b7917 Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.94 | [+0.89, +0.99] | 1 | Logs |
➖ | file_tree | memory utilization | +0.67 | [+0.53, +0.80] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | +0.47 | [+0.40, +0.53] | 1 | Logs bounds checks dashboard |
➖ | docker_containers_memory | memory utilization | +0.31 | [+0.23, +0.38] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | +0.30 | [+0.14, +0.46] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | +0.06 | [-0.54, +0.65] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | +0.04 | [-0.20, +0.27] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | +0.03 | [-0.56, +0.61] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.02, +0.02] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.27, +0.25] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | -0.01 | [-0.55, +0.53] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.03 | [-0.61, +0.55] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.04 | [-0.63, +0.56] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | -0.05 | [-0.65, +0.56] | 1 | Logs |
➖ | docker_containers_cpu | % cpu utilization | -0.05 | [-3.05, +2.95] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | -0.09 | [-0.76, +0.57] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | -0.12 | [-0.18, -0.06] | 1 | Logs |
➖ | ddot_metrics | memory utilization | -0.13 | [-0.25, -0.02] | 1 | Logs |
➖ | ddot_logs | memory utilization | -0.28 | [-0.40, -0.16] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | -0.40 | [-0.53, -0.27] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -0.48 | [-0.56, -0.40] | 1 | Logs bounds checks dashboard |
➖ | quality_gate_logs | % cpu utilization | -1.22 | [-4.00, +1.57] | 1 | Logs bounds checks dashboard |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -1.29 | [-2.18, -0.40] | 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_0ms_latency_http1 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency_linear_load | 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_300ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_300ms_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 |
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:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
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.
-
Its configuration does not mark it "erratic".
CI Pass/Fail Decision
✅ Passed. All Quality Gates passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, 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.
- 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.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
Bumps github.com/samber/lo from 1.49.1 to 1.51.0.
Release notes
Sourced from github.com/samber/lo's releases.
... (truncated)
Commits
203faca
bump v1.51.049f24de
style: merge assertion.go and errors.goe9281d8
feat(assertions): addAssert
andAssertf
(#638)2b57de7
docs: fix wrong variable name for mutable map example (#637)f2cfb22
docs: Fix description for LastOrEmpty and LastOr (#636)52ad90c
doc: Improve comment for lo.Ellipsisf1dce8f
docs: Add a more precise description to the Ellipsis function to prevent misu...a9a589c
fix(ci): correct cleanup deps - remove all *_test.go files using find (#630)975e837
chore(deps): bump golangci/golangci-lint-action from 7 to 8 (#628)3a534ad
Fixed the error in the usage example of lo.Latest in readme.md (#627)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)