Benchmarks

Benchmark execution time: 2025-09-16 16:01:46

Comparing candidate commit bee2c44 in PR branch dario.castane/quick-fix-incident-43109 with baseline commit ca6a4cf in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 24 metrics, 0 unstable metrics.

would we need to add some commands to "go get" these packages in the PACKAGES" directories? (i.e. ./internal/... ./ddtrace/... ./profiler/... ./appsec/... ./instrumentation/...`)

would we need to add some commands to "go get" these packages in the PACKAGES" directories? (i.e. ./internal/... ./ddtrace/... ./profiler/... ./appsec/... ./instrumentation/...`)

We don't need to, as these packages are part of the root module. The other nested modules are updated when running this command:

for d in `find . -iname go.mod | xargs -n1 dirname`; do pushd $d; go mod tidy; popd; done;

/merge

View all feedbacks in Devflow UI.

2025-09-16 16:26:56 UTC ℹ️ Start processing command /merge

2025-09-16 16:27:10 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.

2025-09-16 16:43:37 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in main is approximately 15m (p90).

2025-09-16 16:58:45 UTC ℹ️ MergeQueue: This merge request was merged