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

Bump golang.org/x/arch from 0.11.0 to 0.12.0 #30965

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 11, 2024

Bumps golang.org/x/arch from 0.11.0 to 0.12.0.

Commits
  • f23035d riscv64: add tests for riscv64asm
  • f977c2e s390x/s390xasm: fix self-assignment error
  • ec82f99 README: mention the git repo
  • 153a480 s390x: add s390x disassembler support for the plan9
  • 76fb3b0 s390x: fix decoding several gnu instructions
  • bc8e2b9 ppc64/ppc64asm: speed up PPC64 instruction decoding
  • See full diff in compare view

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 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)

@dependabot dependabot bot added changelog/no-changelog dependencies PRs that bump a dependency dependencies-go PRs that bump a go dependency team/triage labels Nov 11, 2024
@github-actions github-actions bot added the short review PR is simple enough to be reviewed quickly label Nov 11, 2024
Copy link

cit-pr-commenter bot commented Nov 11, 2024

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 5142811a-7b74-4aca-b5e3-50ce89e50b04

Baseline: dc71f1e
Comparison: 0f09397
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
otel_to_otel_logs ingress throughput +0.45 [-0.24, +1.13] 1 Logs
file_tree memory utilization +0.25 [+0.12, +0.37] 1 Logs
quality_gate_idle memory utilization +0.16 [+0.12, +0.21] 1 Logs bounds checks dashboard
file_to_blackhole_100ms_latency egress throughput +0.09 [-0.24, +0.42] 1 Logs
file_to_blackhole_1000ms_latency_linear_load egress throughput +0.07 [-0.42, +0.55] 1 Logs
uds_dogstatsd_to_api_cpu % cpu utilization +0.05 [-0.67, +0.76] 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.00 [-0.47, +0.47] 1 Logs
uds_dogstatsd_to_api ingress throughput -0.01 [-0.09, +0.08] 1 Logs
file_to_blackhole_1000ms_latency egress throughput -0.02 [-0.50, +0.47] 1 Logs
file_to_blackhole_300ms_latency egress throughput -0.05 [-0.24, +0.14] 1 Logs
file_to_blackhole_500ms_latency egress throughput -0.08 [-0.33, +0.16] 1 Logs
tcp_syslog_to_blackhole ingress throughput -0.17 [-0.22, -0.12] 1 Logs
basic_py_check % cpu utilization -0.20 [-4.03, +3.62] 1 Logs
quality_gate_idle_all_features memory utilization -0.21 [-0.30, -0.12] 1 Logs bounds checks dashboard
pycheck_lots_of_tags % cpu utilization -3.95 [-7.33, -0.58] 1 Logs

Bounds Checks: ❌ Failed

perf experiment bounds_check_name replicates_passed links
file_to_blackhole_100ms_latency lost_bytes 5/10
quality_gate_idle memory_usage 6/10 bounds checks dashboard
file_to_blackhole_0ms_latency lost_bytes 7/10
file_to_blackhole_0ms_latency 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 memory_usage 10/10
file_to_blackhole_300ms_latency memory_usage 10/10
file_to_blackhole_500ms_latency memory_usage 10/10
quality_gate_idle_all_features 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".

@paulcacheux paulcacheux added team/networks qa/done QA done before merge and regressions are covered by tests and removed team/triage labels Nov 12, 2024
@paulcacheux
Copy link
Contributor

/merge

@dd-devflow
Copy link

dd-devflow bot commented Nov 12, 2024

Devflow running: /merge

View all feedbacks in Devflow UI.


2024-11-12 07:08:37 UTC ℹ️ MergeQueue: waiting for PR to be ready

This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.


2024-11-12 07:09:40 UTC ℹ️ MergeQueue: pull request added to the queue

The median merge time in main is 23m.


2024-11-12 07:48:22 UTC 🚨 MergeQueue: This merge request is in error

mergequeue build completed successfully, but the github api returned an error while merging the pr.
GitHub returned an error during the merge attempt. This is a known issue that can often be resolved by retrying the merge request in an hour.

Details

Error: PUT https://api.github.com/repos/DataDog/datadog-agent/pulls/30965/merge: 405 Merge already in progress []

FullStacktrace:
activity error (type: github.GithubService_MergePullRequest, scheduledEventID: 41, startedEventID: 42, identity: 1@github-worker-656949d4b6-8w4ct@): PUT https://api.github.com/repos/DataDog/datadog-agent/pulls/30965/merge: 405 Merge already in progress [] (type: GitFailure, retryable: false): PUT https://api.github.com/repos/DataDog/datadog-agent/pulls/30965/merge: 405 Merge already in progress [] (type: ErrorResponse, retryable: true)

@paulcacheux
Copy link
Contributor

/merge

@dd-devflow
Copy link

dd-devflow bot commented Nov 12, 2024

Devflow running: /merge

View all feedbacks in Devflow UI.


2024-11-12 08:09:24 UTC ℹ️ MergeQueue: pull request added to the queue

The median merge time in main is 23m.


2024-11-12 08:32:32 UTC 🚨 MergeQueue: This merge request is in error

mergequeue build completed successfully, but the github api returned an error while merging the pr.
GitHub returned an error during the merge attempt. This is a known issue that can often be resolved by retrying the merge request in an hour.

Details

Error: PUT https://api.github.com/repos/DataDog/datadog-agent/pulls/30965/merge: 405 Merge already in progress []

FullStacktrace:
activity error (type: github.GithubService_MergePullRequest, scheduledEventID: 41, startedEventID: 42, identity: 1@github-worker-7fc65fbc6f-6b529@): PUT https://api.github.com/repos/DataDog/datadog-agent/pulls/30965/merge: 405 Merge already in progress [] (type: GitFailure, retryable: false): PUT https://api.github.com/repos/DataDog/datadog-agent/pulls/30965/merge: 405 Merge already in progress [] (type: ErrorResponse, retryable: true)

@dependabot dependabot bot force-pushed the dependabot/go_modules/golang.org/x/arch-0.12.0 branch from 66bc5f8 to 0f09397 Compare November 12, 2024 11:43
@paulcacheux
Copy link
Contributor

@dependabot rebase

Bumps [golang.org/x/arch](https://github.com/golang/arch) from 0.11.0 to 0.12.0.
- [Commits](golang/arch@v0.11.0...v0.12.0)

---
updated-dependencies:
- dependency-name: golang.org/x/arch
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/go_modules/golang.org/x/arch-0.12.0 branch from 0f09397 to a8917ac Compare November 17, 2024 17:42
Copy link
Contributor Author

dependabot bot commented on behalf of github Nov 18, 2024

Looks like golang.org/x/arch is up-to-date now, so this is no longer needed.

@dependabot dependabot bot closed this Nov 18, 2024
@dependabot dependabot bot deleted the dependabot/go_modules/golang.org/x/arch-0.12.0 branch November 18, 2024 17:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/no-changelog dependencies PRs that bump a dependency dependencies-go PRs that bump a go dependency qa/done QA done before merge and regressions are covered by tests short review PR is simple enough to be reviewed quickly team/networks
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant