Bump ts-graphviz/setup-graphviz from 1 to 2

[dependabot[bot]]

Bumps ts-graphviz/setup-graphviz from 1 to 2.

Release notes

Sourced from ts-graphviz/setup-graphviz's releases.

v2.0.0🌈

Full Changelog: https://github.com/ts-graphviz/setup-graphviz/compare/v1.2.0...v2.0.0

Breaking Changes

• The Codecov Action runs as a node20 action due to node16 deprecation. #558
  • See this post from GitHub on how to migrate.
• Fixed a fatal typo. #507
  • The version variable for windows was window-graphviz-version instead of windows-graphviz-version.

Special thanks for @​joshstrohminger and @​Maetveis ✨

v1.2.0 🌈

Full Changelog: https://github.com/ts-graphviz/setup-graphviz/compare/v1.1...v1.2.0

Add skip repository update flag

A flag to specify whether or not to update the package manager's repositories, allowing users to arbitrarily choose whether or not to update.

This fixes the following issues(#457).

- name: Setup Graphviz
  uses: ts-graphviz/setup-graphviz@v1
  with:
    # Skip to run apt update command on Ubuntu.
    ubuntu-skip-apt-update: 'true' # defalt false
    # Skip to run brew update command on macOS.
    macos-skip-brew-update: 'true' # defalt false

Special thanks for @​jbms and @​mvrueden :sparkles:

v1.1.0 🌈

Full Changelog: https://github.com/ts-graphviz/setup-graphviz/compare/v1.0.1...v1.1.0

Added support for strict version specification feature in Ubuntu and Windows(non-macos) Runner.

- uses: ts-graphviz/setup-graphviz@v1
  with:
    ubuntu-graphviz-version: '2.42.2-3build2'
    ubuntu-libgraphvizdev-version: '2.42.2-3build2'
    windows-graphviz-version: '2.49.3'

Special thanks for @​stunney :sparkles:

v1.0.1 🌈

Full Changelog: https://github.com/ts-graphviz/setup-graphviz/commits/v1.0.1

... (truncated)

Commits

• d5b2b6b feat: build for release
• See full diff in compare view

You can trigger a rebase of this PR 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)

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dependabot[bot]]

The following labels could not be found: dependencies-github-actions.

[pr-commenter[bot]]

Bloop Bleep... Dogbot Here

Regression Detector Results

Run ID: 6f1982bf-f787-4848-a9ff-17b152566402 Baseline: 070f8d1fb2afbe904ee933283cefca107350663b Comparison: e7310ed04cc2ddcdf01fe9877bd5e7d165cc531b 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.

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	file_to_blackhole	% cpu utilization	+0.93	[-5.63, +7.50]
➖	idle	memory utilization	+0.02	[-0.00, +0.04]
➖	file_tree	memory utilization	-0.18	[-0.24, -0.11]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	otel_to_otel_logs	ingress throughput	+1.22	[+0.49, +1.95]
➖	file_to_blackhole	% cpu utilization	+0.93	[-5.63, +7.50]
➖	tcp_syslog_to_blackhole	ingress throughput	+0.73	[+0.67, +0.78]
➖	process_agent_real_time_mode	memory utilization	+0.28	[+0.25, +0.31]
➖	process_agent_standard_check_with_stats	memory utilization	+0.12	[+0.08, +0.17]
➖	process_agent_standard_check	memory utilization	+0.03	[-0.02, +0.07]
➖	idle	memory utilization	+0.02	[-0.00, +0.04]
➖	trace_agent_json	ingress throughput	+0.02	[-0.01, +0.04]
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.06, +0.06]
➖	uds_dogstatsd_to_api	ingress throughput	-0.00	[-0.03, +0.03]
➖	trace_agent_msgpack	ingress throughput	-0.05	[-0.07, -0.02]
➖	file_tree	memory utilization	-0.18	[-0.24, -0.11]
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-1.03	[-2.45, +0.38]

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

[duncanpharvey]

/merge

[dd-devflow[bot]]

:steam_locomotive: MergeQueue

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.

Use /merge -c to cancel this operation!

[agent-platform-auto-pr[bot]]

[Fast Unit Tests Report]

On pipeline 31974493 (CI Visibility). The following jobs did not run any unit tests:

Jobs:

• tests_deb-arm64-py3
• tests_deb-x64-py3
• tests_flavor_dogstatsd_deb-x64
• tests_flavor_heroku_deb-x64
• tests_flavor_iot_deb-x64
• tests_rpm-arm64-py3
• tests_rpm-x64-py3
• 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-developer-experience

[dd-devflow[bot]]

:steam_locomotive: MergeQueue

Pull request added to the queue.

There are 2 builds ahead! (estimated merge in less than 1h)

Use /merge -c to cancel this operation!

[dd-devflow[bot]]

:x: MergeQueue

This merge request conflicts with another merge request ahead in the queue.

The merge requests in front of this one are:

• #24600 with merge sha 7031e35
• #22590 with merge sha db4cbf2

If you need support, contact us on Slack #devflow with those details!

[pr-commenter[bot]]

Regression Detector

Regression Detector Results

Run ID: daa35764-528f-4e3c-b303-a4465c797c1f Baseline: 74fae3f4afeb77720e6584cccbbe853b5c9d677d Comparison: 886ddfa1d48784a76d34002e0f51e49a4e669ed2

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.

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	file_to_blackhole	% cpu utilization	-5.39	[-11.02, +0.24]

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI
➖	idle	memory utilization	+0.61	[+0.56, +0.65]
➖	process_agent_standard_check	memory utilization	+0.60	[+0.54, +0.65]
➖	process_agent_standard_check_with_stats	memory utilization	+0.03	[-0.02, +0.07]
➖	trace_agent_json	ingress throughput	+0.02	[-0.00, +0.05]
➖	uds_dogstatsd_to_api	ingress throughput	+0.02	[-0.18, +0.22]
➖	process_agent_real_time_mode	memory utilization	+0.01	[-0.04, +0.06]
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.04, +0.04]
➖	trace_agent_msgpack	ingress throughput	-0.00	[-0.00, +0.00]
➖	pycheck_1000_100byte_tags	% cpu utilization	-0.11	[-5.02, +4.80]
➖	otel_to_otel_logs	ingress throughput	-0.18	[-0.62, +0.27]
➖	tcp_syslog_to_blackhole	ingress throughput	-0.30	[-0.39, -0.22]
➖	file_tree	memory utilization	-0.45	[-0.57, -0.33]
➖	basic_py_check	% cpu utilization	-1.02	[-3.43, +1.40]
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	-1.76	[-4.67, +1.14]
➖	file_to_blackhole	% cpu utilization	-5.39	[-11.02, +0.24]

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

[duncanpharvey]

/merge

[dd-devflow[bot]]

:steam_locomotive: MergeQueue

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.

Use /merge -c to cancel this operation!

[duncanpharvey]

/remove

[dd-devflow[bot]]

:steam_locomotive: Devflow: /remove

[dd-devflow[bot]]

:warning: MergeQueue

This merge request was unqueued

If you need support, contact us on Slack #devflow!

[duncanpharvey]

/merge

[dd-devflow[bot]]

:steam_locomotive: MergeQueue

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.

Use /merge -c to cancel this operation!

[dd-devflow[bot]]

:warning: MergeQueue

This merge request was unqueued

If you need support, contact us on Slack #devflow!

[duncanpharvey]

/merge

[dd-devflow[bot]]

:steam_locomotive: MergeQueue

Pull request added to the queue.

This build is going to start soon! (estimated merge in less than 24m)

Use /merge -c to cancel this operation!