Skip to content
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 the zstd group with 1 update #20199

Merged
merged 1 commit into from
Apr 1, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 28, 2024

Bumps the zstd group with 1 update: zstd.

Updates zstd from 0.13.0 to 0.13.1

Commits

Dependabot compatibility score

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot dependabot bot added domain: deps Anything related to Vector's dependencies no-changelog Changes in this PR do not need user-facing explanations in the release changelog labels Mar 28, 2024
@jszwedko jszwedko enabled auto-merge March 29, 2024 01:51
@jszwedko jszwedko added this pull request to the merge queue Mar 29, 2024
Copy link

Regression Detector Results

Run ID: fa4d0090-d3e8-4baf-944e-7f2264c712df
Baseline: 333c424
Comparison: f04ee31
Total CPUs: 7

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
syslog_humio_logs ingress throughput +2.86 [+2.76, +2.96]
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput +2.65 [+2.53, +2.77]
syslog_log2metric_splunk_hec_metrics ingress throughput +1.56 [+1.40, +1.72]
datadog_agent_remap_datadog_logs_acks ingress throughput +0.87 [+0.78, +0.95]
http_elasticsearch ingress throughput +0.86 [+0.79, +0.93]
syslog_splunk_hec_logs ingress throughput +0.84 [+0.77, +0.90]
datadog_agent_remap_datadog_logs ingress throughput +0.19 [+0.09, +0.30]
otlp_grpc_to_blackhole ingress throughput +0.16 [+0.07, +0.25]
syslog_loki ingress throughput +0.15 [+0.10, +0.20]
http_to_http_json ingress throughput +0.07 [-0.01, +0.15]
http_to_http_noack ingress throughput +0.04 [-0.07, +0.15]
splunk_hec_to_splunk_hec_logs_acks ingress throughput +0.00 [-0.16, +0.16]
splunk_hec_indexer_ack_blackhole ingress throughput -0.00 [-0.15, +0.14]
http_to_http_acks ingress throughput -0.02 [-1.38, +1.34]
enterprise_http_to_http ingress throughput -0.03 [-0.11, +0.04]
splunk_hec_to_splunk_hec_logs_noack ingress throughput -0.04 [-0.15, +0.08]
http_to_s3 ingress throughput -0.25 [-0.53, +0.03]
http_text_to_http_json ingress throughput -0.26 [-0.40, -0.12]
datadog_agent_remap_blackhole ingress throughput -0.58 [-0.67, -0.49]
splunk_hec_route_s3 ingress throughput -0.76 [-1.22, -0.31]
fluent_elasticsearch ingress throughput -0.78 [-1.26, -0.30]
file_to_blackhole egress throughput -1.03 [-3.62, +1.55]
socket_to_socket_blackhole ingress throughput -1.11 [-1.17, -1.04]
datadog_agent_remap_blackhole_acks ingress throughput -1.34 [-1.44, -1.25]
syslog_regex_logs2metric_ddmetrics ingress throughput -2.22 [-2.35, -2.09]
otlp_http_to_blackhole ingress throughput -2.98 [-3.12, -2.83]
syslog_log2metric_humio_metrics ingress throughput -3.90 [-4.00, -3.80]

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

@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Mar 29, 2024
Copy link

Regression Detector Results

Run ID: d6f2ec00-6a34-4848-89fe-f064e7d9a81d
Baseline: 06f3ad3
Comparison: 3819680
Total CPUs: 7

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
otlp_http_to_blackhole ingress throughput +1.36 [+1.20, +1.53]
http_to_http_acks ingress throughput +1.33 [-0.03, +2.69]
datadog_agent_remap_blackhole_acks ingress throughput +1.02 [+0.89, +1.15]
socket_to_socket_blackhole ingress throughput +0.79 [+0.72, +0.86]
datadog_agent_remap_datadog_logs_acks ingress throughput +0.78 [+0.69, +0.87]
http_to_http_noack ingress throughput +0.10 [+0.01, +0.19]
http_to_http_json ingress throughput +0.05 [-0.03, +0.12]
splunk_hec_to_splunk_hec_logs_acks ingress throughput -0.00 [-0.16, +0.16]
splunk_hec_indexer_ack_blackhole ingress throughput -0.01 [-0.15, +0.14]
http_to_s3 ingress throughput -0.02 [-0.30, +0.26]
fluent_elasticsearch ingress throughput -0.03 [-0.51, +0.45]
syslog_log2metric_humio_metrics ingress throughput -0.04 [-0.13, +0.06]
splunk_hec_to_splunk_hec_logs_noack ingress throughput -0.06 [-0.17, +0.06]
enterprise_http_to_http ingress throughput -0.07 [-0.14, +0.00]
datadog_agent_remap_blackhole ingress throughput -0.40 [-0.49, -0.32]
otlp_grpc_to_blackhole ingress throughput -0.53 [-0.61, -0.44]
datadog_agent_remap_datadog_logs ingress throughput -0.59 [-0.69, -0.48]
http_text_to_http_json ingress throughput -0.68 [-0.80, -0.56]
http_elasticsearch ingress throughput -0.79 [-0.86, -0.71]
syslog_regex_logs2metric_ddmetrics ingress throughput -0.82 [-0.95, -0.68]
splunk_hec_route_s3 ingress throughput -0.86 [-1.32, -0.40]
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput -1.78 [-1.89, -1.67]
syslog_loki ingress throughput -2.85 [-2.90, -2.80]
file_to_blackhole egress throughput -2.98 [-5.32, -0.64]
syslog_splunk_hec_logs ingress throughput -3.07 [-3.13, -3.01]
syslog_log2metric_splunk_hec_metrics ingress throughput -4.20 [-4.34, -4.06]
syslog_humio_logs ingress throughput -4.32 [-4.43, -4.21]

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

@dependabot dependabot bot force-pushed the dependabot/cargo/zstd-69d6ea5509 branch from 330eea9 to 743ce30 Compare March 29, 2024 19:15
Bumps the zstd group with 1 update: [zstd](https://github.com/gyscos/zstd-rs).


Updates `zstd` from 0.13.0 to 0.13.1
- [Release notes](https://github.com/gyscos/zstd-rs/releases)
- [Commits](gyscos/zstd-rs@v0.13.0...v0.13.1)

---
updated-dependencies:
- dependency-name: zstd
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: zstd
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/cargo/zstd-69d6ea5509 branch from 743ce30 to 896f49b Compare April 1, 2024 04:03
@jszwedko jszwedko added this pull request to the merge queue Apr 1, 2024
Copy link

github-actions bot commented Apr 1, 2024

Regression Detector Results

Run ID: fa7af867-f8cb-4536-8c67-ed46fc42bacb
Baseline: 5ffb1a5
Comparison: 0599d60
Total CPUs: 7

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
syslog_splunk_hec_logs ingress throughput +2.21 [+2.13, +2.30]
splunk_hec_route_s3 ingress throughput +1.69 [+1.23, +2.16]
datadog_agent_remap_blackhole_acks ingress throughput +1.47 [+1.33, +1.60]
file_to_blackhole egress throughput +0.99 [-1.49, +3.48]
http_to_s3 ingress throughput +0.61 [+0.33, +0.89]
otlp_http_to_blackhole ingress throughput +0.57 [+0.42, +0.72]
datadog_agent_remap_datadog_logs_acks ingress throughput +0.32 [+0.23, +0.41]
syslog_loki ingress throughput +0.14 [+0.07, +0.21]
http_to_http_noack ingress throughput +0.10 [+0.01, +0.19]
http_to_http_acks ingress throughput +0.08 [-1.28, +1.45]
http_to_http_json ingress throughput +0.01 [-0.06, +0.08]
splunk_hec_to_splunk_hec_logs_acks ingress throughput +0.00 [-0.16, +0.16]
splunk_hec_indexer_ack_blackhole ingress throughput -0.01 [-0.15, +0.13]
fluent_elasticsearch ingress throughput -0.02 [-0.50, +0.45]
enterprise_http_to_http ingress throughput -0.07 [-0.14, +0.01]
splunk_hec_to_splunk_hec_logs_noack ingress throughput -0.08 [-0.19, +0.03]
syslog_log2metric_splunk_hec_metrics ingress throughput -0.34 [-0.50, -0.18]
datadog_agent_remap_datadog_logs ingress throughput -0.42 [-0.56, -0.27]
http_elasticsearch ingress throughput -0.63 [-0.72, -0.54]
http_text_to_http_json ingress throughput -0.65 [-0.79, -0.50]
otlp_grpc_to_blackhole ingress throughput -0.89 [-0.98, -0.80]
syslog_humio_logs ingress throughput -0.97 [-1.07, -0.86]
syslog_log2metric_tag_cardinality_limit_blackhole ingress throughput -1.22 [-1.36, -1.07]
socket_to_socket_blackhole ingress throughput -1.29 [-1.38, -1.20]
datadog_agent_remap_blackhole ingress throughput -1.59 [-1.73, -1.45]
syslog_regex_logs2metric_ddmetrics ingress throughput -2.58 [-2.76, -2.40]
syslog_log2metric_humio_metrics ingress throughput -2.65 [-2.79, -2.51]

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

Merged via the queue into master with commit 0599d60 Apr 1, 2024
50 checks passed
@jszwedko jszwedko deleted the dependabot/cargo/zstd-69d6ea5509 branch April 1, 2024 18:03
jszwedko added a commit that referenced this pull request Apr 24, 2024
github-merge-queue bot pushed a commit that referenced this pull request Apr 25, 2024
* chore(dev): Bump down zstd-sys from 2.0.10 to 2.0.9

To fix a WASM build issue. We can upgrade again once gyscos/zstd-rs#274 is
merged and released (or gyscos/zstd-rs#271 is otherwise fixed).

Also add a test that builds the playground to catch this sort of regression in the future.

Signed-off-by: Jesse Szwedko <[email protected]>

* Revert "chore(deps): Bump the zstd group with 1 update (#20199)"

This reverts commit 0599d60.

Signed-off-by: Jesse Szwedko <[email protected]>

* chmod +x

Signed-off-by: Jesse Szwedko <[email protected]>

* Just put directly in env prepare

Signed-off-by: Jesse Szwedko <[email protected]>

* Bump timeout

Signed-off-by: Jesse Szwedko <[email protected]>

---------

Signed-off-by: Jesse Szwedko <[email protected]>
AndrooTheChen pushed a commit to discord/vector that referenced this pull request Sep 23, 2024
Bumps the zstd group with 1 update: [zstd](https://github.com/gyscos/zstd-rs).


Updates `zstd` from 0.13.0 to 0.13.1
- [Release notes](https://github.com/gyscos/zstd-rs/releases)
- [Commits](gyscos/zstd-rs@v0.13.0...v0.13.1)

---
updated-dependencies:
- dependency-name: zstd
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: zstd
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
AndrooTheChen pushed a commit to discord/vector that referenced this pull request Sep 23, 2024
* chore(dev): Bump down zstd-sys from 2.0.10 to 2.0.9

To fix a WASM build issue. We can upgrade again once gyscos/zstd-rs#274 is
merged and released (or gyscos/zstd-rs#271 is otherwise fixed).

Also add a test that builds the playground to catch this sort of regression in the future.

Signed-off-by: Jesse Szwedko <[email protected]>

* Revert "chore(deps): Bump the zstd group with 1 update (vectordotdev#20199)"

This reverts commit 0599d60.

Signed-off-by: Jesse Szwedko <[email protected]>

* chmod +x

Signed-off-by: Jesse Szwedko <[email protected]>

* Just put directly in env prepare

Signed-off-by: Jesse Szwedko <[email protected]>

* Bump timeout

Signed-off-by: Jesse Szwedko <[email protected]>

---------

Signed-off-by: Jesse Szwedko <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain: deps Anything related to Vector's dependencies no-changelog Changes in this PR do not need user-facing explanations in the release changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant