datadog-agent
datadog-agent copied to clipboard
Bump golang.org/x/crypto from 0.26.0 to 0.27.0 in /test/new-e2e
Bumps golang.org/x/crypto from 0.26.0 to 0.27.0.
Commits
c9da6b9all: fix printf(var) mistakes detected by latest printf checkerb35ab4fgo.mod: update golang.org/x dependenciesbcb0f91internal/poly1305: Port sum_amd64.s to Avo7eace71chacha20poly1305: Avo port of chacha20poly1305_amd64.s620dfbcsalsa20/salsa: Port salsa20_amd64.s to Avo82942cfblake2b: port blake2b_amd64.s to Avo0484c26blake2b: port blake2bAVX2_amd64.s to Avo38ed1bcblake2s: port blake2s_amd64.s to Avo38a0b5dargon2: Avo port of blamka_amd64.sbf5f14fx509roots/fallback: update bundle- 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Regression Detector
Regression Detector Results
Run ID: 8065dde3-1b59-4083-b370-897e3404a44d Metrics dashboard Target profiles
Baseline: 6e8be0f4c7c62466c91d3f5ff22ed5092fea8945 Comparison: 699789b423c5ebc010f31e180369b7b593974bf5
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 | trials | links |
|---|---|---|---|---|---|---|
| ➖ | basic_py_check | % cpu utilization | +1.03 | [-1.70, +3.77] | 1 | Logs |
| ➖ | pycheck_lots_of_tags | % cpu utilization | +0.81 | [-1.73, +3.35] | 1 | Logs |
| ➖ | file_tree | memory utilization | +0.25 | [+0.16, +0.34] | 1 | Logs |
| ➖ | idle_all_features | memory utilization | +0.21 | [+0.14, +0.28] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | +0.02 | [-0.07, +0.12] | 1 | Logs |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.01, +0.01] | 1 | Logs |
| ➖ | idle | memory utilization | -0.03 | [-0.07, +0.01] | 1 | Logs |
| ➖ | otel_to_otel_logs | ingress throughput | -0.14 | [-0.95, +0.66] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.36 | [-1.10, +0.37] | 1 | Logs |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | -1.00 | [-1.07, -0.92] | 1 | Logs |
Bounds Checks
| perf | experiment | bounds_check_name | replicates_passed |
|---|---|---|---|
| ✅ | idle | memory_usage | 10/10 |
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:
-
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".
[Fast Unit Tests Report]
On pipeline 45508711 (CI Visibility). The following jobs did not run any unit tests:
Jobs:
- tests_windows-x64
If you modified Go files and expected unit tests to run in these jobs, please double check the job logs. If you think tests should have been executed reach out to #agent-devx-help
Looks like golang.org/x/crypto is up-to-date now, so this is no longer needed.