-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
chore(deps): Bump serde_json from 1.0.128 to 1.0.132 #21565
Conversation
Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.128 to 1.0.132. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](serde-rs/json@1.0.128...1.0.132) --- updated-dependencies: - dependency-name: serde_json dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/ci-run-regression
Regression Detector ResultsRun ID: 5ceb65ba-6187-43fc-a785-fc8f51d37f01 Metrics dashboard Baseline: dc441a2 Performance changes are noted in the perf column of each table:
Significant changes in experiment optimization goalsConfidence level: 90.00%
|
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
❌ | file_to_blackhole | egress throughput | -5.61 | [-9.66, -1.57] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
✅ | socket_to_socket_blackhole | ingress throughput | +6.62 | [+6.53, +6.70] | |
✅ | syslog_log2metric_splunk_hec_metrics | ingress throughput | +5.10 | [+4.97, +5.22] | |
➖ | http_text_to_http_json | ingress throughput | +3.67 | [+3.50, +3.83] | |
➖ | http_elasticsearch | ingress throughput | +2.83 | [+2.67, +2.99] | |
➖ | syslog_splunk_hec_logs | ingress throughput | +2.37 | [+2.27, +2.48] | |
➖ | syslog_loki | ingress throughput | +1.44 | [+1.36, +1.52] | |
➖ | otlp_http_to_blackhole | ingress throughput | +1.15 | [+1.07, +1.23] | |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | +1.12 | [+0.98, +1.25] | |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | +1.09 | [+1.00, +1.17] | |
➖ | splunk_hec_route_s3 | ingress throughput | +0.61 | [+0.33, +0.90] | |
➖ | syslog_humio_logs | ingress throughput | +0.44 | [+0.32, +0.56] | |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | +0.10 | [-0.05, +0.25] | |
➖ | http_to_http_acks | ingress throughput | +0.04 | [-0.45, +0.53] | |
➖ | http_to_http_noack | ingress throughput | +0.00 | [-0.05, +0.06] | |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | -0.00 | [-0.02, +0.02] | |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.00 | [-0.03, +0.02] | |
➖ | http_to_http_json | ingress throughput | -0.00 | [-0.04, +0.04] | |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | -0.00 | [-0.02, +0.02] | |
➖ | http_to_s3 | ingress throughput | -0.60 | [-0.77, -0.43] | |
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | -0.85 | [-0.98, -0.72] | |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | -1.28 | [-1.46, -1.09] | |
➖ | syslog_log2metric_humio_metrics | ingress throughput | -1.66 | [-1.80, -1.51] | |
➖ | datadog_agent_remap_blackhole | ingress throughput | -2.01 | [-2.16, -1.87] | |
➖ | fluent_elasticsearch | ingress throughput | -2.14 | [-2.69, -1.59] | |
➖ | otlp_grpc_to_blackhole | ingress throughput | -3.49 | [-3.66, -3.31] | |
❌ | file_to_blackhole | egress throughput | -5.61 | [-9.66, -1.57] |
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".
Regression Detector ResultsRun ID: 8c2cb724-3120-4fe5-9b2c-748d9ea5c30e Metrics dashboard Baseline: 86fb074 Performance changes are noted in the perf column of each table:
Significant changes in experiment optimization goalsConfidence level: 90.00%
|
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
➖ | file_to_blackhole | egress throughput | -0.01 | [-4.17, +4.15] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
✅ | otlp_http_to_blackhole | ingress throughput | +6.46 | [+6.38, +6.54] | |
➖ | socket_to_socket_blackhole | ingress throughput | +4.08 | [+4.02, +4.14] | |
➖ | splunk_hec_route_s3 | ingress throughput | +3.26 | [+2.96, +3.55] | |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | +2.04 | [+1.94, +2.13] | |
➖ | syslog_humio_logs | ingress throughput | +1.81 | [+1.67, +1.96] | |
➖ | http_text_to_http_json | ingress throughput | +1.78 | [+1.66, +1.91] | |
➖ | syslog_splunk_hec_logs | ingress throughput | +1.72 | [+1.63, +1.80] | |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | +1.33 | [+1.21, +1.44] | |
➖ | otlp_grpc_to_blackhole | ingress throughput | +1.25 | [+1.08, +1.41] | |
➖ | syslog_loki | ingress throughput | +1.19 | [+1.12, +1.27] | |
➖ | datadog_agent_remap_blackhole | ingress throughput | +0.58 | [+0.50, +0.65] | |
➖ | http_to_s3 | ingress throughput | +0.18 | [+0.02, +0.33] | |
➖ | http_to_http_noack | ingress throughput | +0.00 | [-0.05, +0.06] | |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | -0.00 | [-0.02, +0.02] | |
➖ | http_to_http_json | ingress throughput | -0.00 | [-0.05, +0.05] | |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | -0.00 | [-0.02, +0.02] | |
➖ | file_to_blackhole | egress throughput | -0.01 | [-4.17, +4.15] | |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.01 | [-0.03, +0.01] | |
➖ | http_to_http_acks | ingress throughput | -0.02 | [-0.51, +0.48] | |
➖ | fluent_elasticsearch | ingress throughput | -0.79 | [-1.33, -0.25] | |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | -0.99 | [-1.09, -0.89] | |
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | -1.21 | [-1.36, -1.06] | |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | -1.45 | [-1.64, -1.26] | |
➖ | http_elasticsearch | ingress throughput | -1.59 | [-1.76, -1.42] | |
➖ | syslog_log2metric_humio_metrics | ingress throughput | -1.78 | [-1.93, -1.63] | |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | -3.06 | [-3.23, -2.88] |
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".
Bumps serde_json from 1.0.128 to 1.0.132.
Release notes
Sourced from serde_json's releases.
Commits
86d933c
Release 1.0.132f45b422
Merge pull request #1206 from dtolnay/hasnextf2082d2
Clearer order of comparisons0f54a1a
Handle early return sooner on eof in seq or map2a4cb44
Rearrange 'match peek'4cb90ce
Merge pull request #1205 from dtolnay/hasnextb71ccd2
Reduce duplicative instantiation of logic in SeqAccess and MapAccessa810ba9
Release 1.0.1310d084c5
Touch up PR 1135b4954a9
Merge pull request #1135 from swlynch99/map-deserializerDependabot 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)