Bump build images for python 3.12.6 updates #29963
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Gitlab CI Configuration Changes
|
| Removed | Modified | Added | Renamed |
|---|---|---|---|
| 0 | 28 | 0 | 0 |
ℹ️ Diff available in the job log.
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 80ece75 Optimization Goals: ❌ Significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | basic_py_check | % cpu utilization | +2.99 | [-0.85, +6.83] | 1 | Logs |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | +0.04 | [-0.01, +0.10] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | +0.00 | [-0.42, +0.42] | 1 | Logs |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.01, +0.01] | 1 | Logs |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | -0.00 | [-0.26, +0.25] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | -0.02 | [-0.09, +0.06] | 1 | Logs |
| ➖ | file_to_blackhole_300ms_latency | egress throughput | -0.04 | [-0.23, +0.15] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.08 | [-0.56, +0.41] | 1 | Logs |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | -0.09 | [-0.33, +0.16] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | -0.41 | [-0.46, -0.36] | 1 | Logs bounds checks dashboard |
| ➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.45 | [-1.17, +0.28] | 1 | Logs |
| ➖ | quality_gate_idle_all_features | memory utilization | -0.53 | [-0.66, -0.41] | 1 | Logs bounds checks dashboard |
| ➖ | idle_all_features | memory utilization | -0.59 | [-0.69, -0.49] | 1 | Logs bounds checks dashboard |
| ➖ | idle | memory utilization | -0.78 | [-0.83, -0.74] | 1 | Logs bounds checks dashboard |
| ➖ | file_tree | memory utilization | -1.21 | [-1.35, -1.06] | 1 | Logs |
| ✅ | pycheck_lots_of_tags | % cpu utilization | -6.83 | [-10.08, -3.57] | 1 | Logs |
Bounds Checks: ❌ Failed
| perf | experiment | bounds_check_name | replicates_passed | links |
|---|---|---|---|---|
| ❌ | file_to_blackhole_0ms_latency | lost_bytes | 6/10 | |
| ❌ | file_to_blackhole_100ms_latency | lost_bytes | 7/10 | |
| ❌ | quality_gate_idle | memory_usage | 7/10 | bounds checks dashboard |
| ❌ | idle | memory_usage | 9/10 | bounds checks dashboard |
| ✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
| ✅ | file_to_blackhole_1000ms_latency | 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 | |
| ✅ | idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
| ✅ | 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:
-
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".
Kyle-Neale
force-pushed
the
kyle.neale/test-build-image-updates
branch
from
0fde749
to
e6f93fe
Compare
Kyle-Neale
force-pushed
the
kyle.neale/test-build-image-updates
branch
from
e6f93fe
to
8e0aec4
Compare
Kyle-Neale
force-pushed
the
kyle.neale/test-build-image-updates
branch
from
7a5f48f
to
70d865b
Compare
github-actions
bot
added
the
short review
Kyle-Neale
changed the title
steveny91
approved these changes
Nov 8, 2024
github-actions
bot
added
long review
steveny91
approved these changes
Nov 8, 2024
FlorentClarret
approved these changes
Nov 8, 2024
brycekahle
approved these changes
Nov 8, 2024
|
/merge |
Devflow running:
|
pducolin
added
the
qa/done
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR updates the
buildimagesto 3.12.6Motivation
The embedded python we use in the Agent was bumped so we bump the actual buildimages so we're building in the same Python environment
Describe how to test/QA your changes
This PR should successfully build the agent and run installer tests, asserting we use the expected python version
Possible Drawbacks / Trade-offs
Additional Notes