DataDog
[gitlab] Added print utilities
What does this PR do?
Adds two tasks to inspect / query easily jobs / pipelines.
-j or --jq adds a jq query
Motivation
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes
[Fast Unit Tests Report]
On pipeline 38367600 (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-devx-help
![agent-platform-auto-pr[bot] avatar](https://avatars.githubusercontent.com/u/365230?v=4 "Published by a pub.dev verified publisher"){kind=small}
Regression Detector
Regression Detector Results
Run ID: 58f29f21-c0b7-4603-89b4-9e99e5475961 Metrics dashboard Target profiles
Baseline: a30e11cc4bc65345436170a340e335180b970e8c Comparison: 0913d6350ffbb787dcd0fb012ecf9ede1effd46a
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 | links |
|---|---|---|---|---|---|
| ➖ | pycheck_1000_100byte_tags | % cpu utilization | +1.06 | [-3.77, +5.88] | Logs |
| ➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.73 | [-0.16, +1.62] | Logs |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.01, +0.01] | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | +0.00 | [-0.00, +0.00] | Logs |
| ➖ | otel_to_otel_logs | ingress throughput | -0.17 | [-0.98, +0.64] | Logs |
| ➖ | file_tree | memory utilization | -0.41 | [-0.46, -0.36] | Logs |
| ➖ | idle | memory utilization | -1.01 | [-1.05, -0.96] | Logs |
| ➖ | basic_py_check | % cpu utilization | -1.03 | [-3.65, +1.59] | Logs |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | -4.46 | [-17.16, +8.24] | Logs |
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".
:steam_locomotive: 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.
Use /merge -c to cancel this operation!
:steam_locomotive: MergeQueue: pull request added to the queue
The median merge time in main is 25m.
Use /merge -c to cancel this operation!
:x: MergeQueue: The build pipeline contains failing jobs for this merge request
Build pipeline has failing jobs for 9496c46
Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail. Therefore, and to allow other builds to be processed, this merge request has been rejected before the end of the pipeline.
You should have a look at the pipeline, wait for the build to finish and investigate the failures. When you are ready, re-add your pull request to the queue!
⚠️ Do NOT retry failed jobs directly.
They were executed on a temporary branch created by the merge queue. If you retry them, they are going to fail because the branch no longer exists.
If you need support, contact us on Slack #devflow with those details!
:steam_locomotive: 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.
Use /merge -c to cancel this operation!
:steam_locomotive: MergeQueue: pull request added to the queue
The median merge time in main is 25m.
Use /merge -c to cancel this operation!