Build python with bazel on unix as well by chouquette · Pull Request #44914 · DataDog/datadog-agent

chouquette · 2026-01-09T08:02:15Z

What does this PR do?

Build python with bazel (through rules_foreign_cc)

Motivation

Migrating our builds to bazel

Describe how you validated your changes

Local builds for linux x86_64, CI for the others

Additional Notes

This is based on top of #43893

chouquette · 2026-01-09T08:15:09Z

/trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable RUN_UNIT_TESTS=on --variable RUN_KMT_TESTS=on

dd-devflow-routing-codex · 2026-01-09T08:15:11Z

View all feedbacks in Devflow UI.

2026-01-09 08:15:11 UTC ℹ️ Start processing command /trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable RUN_UNIT_TESTS=on --variable RUN_KMT_TESTS=on

2026-01-09 08:16:27 UTC ℹ️ Gitlab pipeline started

Started pipeline #89854353

cit-pr-commenter · 2026-01-09T09:08:43Z

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: dbd728d3-245d-448f-a03d-d9f3ef0b9fb3

Baseline: 8766844
Comparison: 4677c0a
Diff

❌ Experiments with retried target crashes

This is a critical error. One or more replicates failed with a non-zero exit code. These replicates may have been retried. See Replicate Execution Details for more information.

docker_containers_memory

Optimization Goals: ✅ No significant changes detected

Experiments ignored for regressions

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

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	docker_containers_cpu	% cpu utilization	+3.86	[+0.72, +7.00]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	docker_containers_cpu	% cpu utilization	+3.86	[+0.72, +7.00]	1	Logs
➖	ddot_metrics_sum_delta	memory utilization	+0.63	[+0.42, +0.84]	1	Logs
➖	ddot_metrics	memory utilization	+0.53	[+0.31, +0.75]	1	Logs
➖	ddot_logs	memory utilization	+0.50	[+0.44, +0.56]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.36	[+0.32, +0.40]	1	Logs bounds checks dashboard
➖	otlp_ingest_metrics	memory utilization	+0.26	[+0.11, +0.42]	1	Logs
➖	quality_gate_idle	memory utilization	+0.18	[+0.14, +0.23]	1	Logs bounds checks dashboard
➖	quality_gate_metrics_logs	memory utilization	+0.16	[-0.06, +0.39]	1	Logs bounds checks dashboard
➖	file_to_blackhole_0ms_latency	egress throughput	+0.05	[-0.46, +0.55]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.03	[-0.01, +0.08]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.02	[-0.11, +0.14]	1	Logs
➖	uds_dogstatsd_to_api_v3	ingress throughput	+0.01	[-0.11, +0.13]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.09, +0.10]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.03	[-0.41, +0.35]	1	Logs
➖	file_tree	memory utilization	-0.04	[-0.09, +0.02]	1	Logs
➖	docker_containers_memory	memory utilization	-0.06	[-0.14, +0.02]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.07	[-0.48, +0.35]	1	Logs
➖	ddot_metrics_sum_cumulativetodelta_exporter	memory utilization	-0.08	[-0.31, +0.15]	1	Logs
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	-0.20	[-0.25, -0.14]	1	Logs
➖	otlp_ingest_logs	memory utilization	-0.24	[-0.35, -0.13]	1	Logs
➖	ddot_metrics_sum_cumulative	memory utilization	-0.27	[-0.43, -0.11]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-0.96	[-1.01, -0.91]	1	Logs
➖	quality_gate_logs	% cpu utilization	-1.94	[-3.42, -0.47]	1	Logs bounds checks dashboard

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	links
✅	docker_containers_cpu	simple_check_run	10/10
✅	docker_containers_memory	memory_usage	10/10
✅	docker_containers_memory	simple_check_run	10/10
✅	file_to_blackhole_0ms_latency	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency	lost_bytes	10/10
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10
✅	file_to_blackhole_100ms_latency	lost_bytes	10/10
✅	file_to_blackhole_100ms_latency	memory_usage	10/10
✅	file_to_blackhole_500ms_latency	lost_bytes	10/10
✅	file_to_blackhole_500ms_latency	memory_usage	10/10
✅	quality_gate_idle	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_logs	lost_bytes	10/10	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	lost_bytes	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	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".

Replicate Execution Details

We run multiple replicates for each experiment/variant. However, we allow replicates to be automatically retried if there are any failures, up to 8 times, at which point the replicate is marked dead and we are unable to run analysis for the entire experiment. We call each of these attempts at running replicates a replicate execution. This section lists all replicate executions that failed due to the target crashing or being oom killed.

Note: In the below tables we bucket failures by experiment, variant, and failure type. For each of these buckets we list out the replicate indexes that failed with an annotation signifying how many times said replicate failed with the given failure mode. In the below example the baseline variant of the experiment named experiment_with_failures had two replicates that failed by oom kills. Replicate 0, which failed 8 executions, and replicate 1 which failed 6 executions, all with the same failure mode.

Experiment	Variant	Replicates	Failure	Logs	Debug Dashboard
experiment_with_failures	baseline	0 (x8) 1 (x6)	Oom killed		Debug Dashboard

The debug dashboard links will take you to a debugging dashboard specifically designed to investigate replicate execution failures.

❌ Retried Normal Replicate Execution Failures (non-profiling)

Experiment	Variant	Replicates	Failure	Debug Dashboard
docker_containers_memory	baseline	8	Failed to shutdown when requested	Debug Dashboard

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
quality_gate_metrics_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.

agent-platform-auto-pr · 2026-01-09T11:23:28Z

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor 8766844
📊 Static Quality Gates Dashboard

Successful checks

Info

	Quality gate	Change	Size (prev → curr → max)
✅	agent_deb_amd64	-79.06 KiB (0.01% reduction)	752.511 → 752.434 → 754.830
✅	agent_deb_amd64_fips	-78.94 KiB (0.01% reduction)	701.180 → 701.103 → 704.000
✅	agent_heroku_amd64	-337.08 KiB (0.10% reduction)	326.974 → 326.644 → 329.530
✅	agent_rpm_amd64	-79.06 KiB (0.01% reduction)	752.495 → 752.417 → 754.800
✅	agent_rpm_amd64_fips	-78.94 KiB (0.01% reduction)	701.164 → 701.086 → 703.990
✅	agent_rpm_arm64	-60.22 KiB (0.01% reduction)	731.268 → 731.209 → 737.340
✅	agent_rpm_arm64_fips	-60.1 KiB (0.01% reduction)	683.256 → 683.197 → 688.480
✅	agent_suse_amd64	-79.06 KiB (0.01% reduction)	752.495 → 752.417 → 754.800
✅	agent_suse_amd64_fips	-78.94 KiB (0.01% reduction)	701.164 → 701.086 → 703.990
✅	agent_suse_arm64	-60.22 KiB (0.01% reduction)	731.268 → 731.209 → 737.340
✅	agent_suse_arm64_fips	-60.1 KiB (0.01% reduction)	683.256 → 683.197 → 688.480
✅	docker_agent_amd64	-79.03 KiB (0.01% reduction)	814.612 → 814.535 → 817.140
✅	docker_agent_arm64	-60.18 KiB (0.01% reduction)	817.976 → 817.917 → 824.020
✅	docker_agent_jmx_amd64	-79.02 KiB (0.01% reduction)	1005.491 → 1005.414 → 1008.020
✅	docker_agent_jmx_arm64	-60.18 KiB (0.01% reduction)	997.574 → 997.515 → 1003.620

16 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_msi	663.055 MiB
✅	docker_cluster_agent_amd64	181.112 MiB
✅	docker_cluster_agent_arm64	196.918 MiB
✅	docker_cws_instrumentation_amd64	7.135 MiB
✅	docker_cws_instrumentation_arm64	6.689 MiB
✅	docker_dogstatsd_amd64	38.840 MiB
✅	docker_dogstatsd_arm64	37.128 MiB
✅	dogstatsd_deb_amd64	30.059 MiB
✅	dogstatsd_deb_arm64	28.204 MiB
✅	dogstatsd_rpm_amd64	30.059 MiB
✅	dogstatsd_suse_amd64	30.059 MiB
✅	iot_agent_deb_amd64	43.037 MiB
✅	iot_agent_deb_arm64	40.135 MiB
✅	iot_agent_deb_armhf	40.705 MiB
✅	iot_agent_rpm_amd64	43.038 MiB
✅	iot_agent_suse_amd64	43.038 MiB

On-wire sizes (compressed)

	Quality gate	Change	Size (prev → curr → max)
✅	agent_deb_amd64	-43.69 KiB (0.02% reduction)	183.949 → 183.907 → 184.810
✅	agent_deb_amd64_fips	+21.62 KiB (0.01% increase)	172.616 → 172.637 → 173.790
✅	agent_heroku_amd64	-37.5 KiB (0.04% reduction)	87.157 → 87.120 → 88.450
✅	agent_msi	-20.0 KiB (0.01% reduction)	143.152 → 143.133 → 143.300
✅	agent_rpm_amd64	-27.73 KiB (0.01% reduction)	186.830 → 186.802 → 188.160
✅	agent_rpm_amd64_fips	-84.59 KiB (0.05% reduction)	175.731 → 175.648 → 176.600
✅	agent_rpm_arm64	-103.04 KiB (0.06% reduction)	168.625 → 168.524 → 169.930
✅	agent_rpm_arm64_fips	-31.12 KiB (0.02% reduction)	159.172 → 159.142 → 160.550
✅	agent_suse_amd64	-27.73 KiB (0.01% reduction)	186.830 → 186.802 → 188.160
✅	agent_suse_amd64_fips	-84.59 KiB (0.05% reduction)	175.731 → 175.648 → 176.600
✅	agent_suse_arm64	-103.04 KiB (0.06% reduction)	168.625 → 168.524 → 169.930
✅	agent_suse_arm64_fips	-31.12 KiB (0.02% reduction)	159.172 → 159.142 → 160.550
✅	docker_agent_amd64	-24.58 KiB (0.01% reduction)	276.622 → 276.598 → 277.400
✅	docker_agent_arm64	-30.25 KiB (0.01% reduction)	264.050 → 264.021 → 266.040
✅	docker_agent_jmx_amd64	-33.35 KiB (0.01% reduction)	345.262 → 345.229 → 346.020
✅	docker_agent_jmx_arm64	-29.49 KiB (0.01% reduction)	328.668 → 328.639 → 330.660
✅	docker_cluster_agent_amd64	neutral	63.994 MiB → 64.490
✅	docker_cluster_agent_arm64	neutral	60.256 MiB → 61.170
✅	docker_cws_instrumentation_amd64	neutral	2.994 MiB → 3.330
✅	docker_cws_instrumentation_arm64	neutral	2.726 MiB → 3.090
✅	docker_dogstatsd_amd64	neutral	15.031 MiB → 15.820
✅	docker_dogstatsd_arm64	neutral	14.356 MiB → 14.830
✅	dogstatsd_deb_amd64	neutral	7.946 MiB → 8.790
✅	dogstatsd_deb_arm64	neutral	6.825 MiB → 7.710
✅	dogstatsd_rpm_amd64	neutral	7.958 MiB → 8.800
✅	dogstatsd_suse_amd64	neutral	7.958 MiB → 8.800
✅	iot_agent_deb_amd64	neutral	11.291 MiB → 12.040
✅	iot_agent_deb_arm64	neutral	9.651 MiB → 10.450
✅	iot_agent_deb_armhf	+2.61 KiB (0.03% increase)	9.844 → 9.847 → 10.620
✅	iot_agent_rpm_amd64	neutral	11.309 MiB → 12.060
✅	iot_agent_suse_amd64	neutral	11.309 MiB → 12.060

aiuto

We seriously need to stop with patch files and vendor in our own copy of rules_foreign_cc. Let's work on it there until is good enough, then push to upstream the changes.
Reviewing patches does not provide enough context.

We need unit tests for replace_prefix. It is too important now. But don't let that block this PR.

chouquette · 2026-01-14T15:21:00Z

I triggered the agent integrations test workflow with the last pipeline docker images: https://github.com/DataDog/integrations-core/actions/runs/20999372170
If all goes well this can be merged after that 🤞

edit: the workflow needs a public image, so I'll run a deploy pipeline & re-run the tests again

chouquette · 2026-01-14T15:27:39Z

/trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable DEPLOY_AGENT=true --variable RUN_UNIT_TESTS=on --variable RUN_KMT_TESTS=on

gh-worker-devflow-routing-ef8351 · 2026-01-14T15:27:43Z

View all feedbacks in Devflow UI.

2026-01-14 15:27:42 UTC ℹ️ Start processing command /trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable DEPLOY_AGENT=true --variable RUN_UNIT_TESTS=on --variable RUN_KMT_TESTS=on

2026-01-14 15:29:14 UTC ℹ️ Gitlab pipeline started

Started pipeline #90697670

chouquette · 2026-01-15T07:58:44Z

https://github.com/DataDog/integrations-core/actions/runs/21023096921/job/60441573571

Error: could not load ibm_mq:
* Core Check Loader: Check ibm_mq not found in Catalog
* Python Check Loader: unable to load check ibm_mq: unable to load python module datadog_checks.ibm_mq: unable to import module 'datadog_checks.ibm_mq': Traceback (most recent call last):
  File "/home/ibm_mq/datadog_checks/ibm_mq/__init__.py", line 5, in <module>
    from .ibm_mq import IbmMqCheck
  File "/home/ibm_mq/datadog_checks/ibm_mq/ibm_mq.py", line 7, in <module>
    from datadog_checks.ibm_mq.collectors.stats_collector import StatsCollector
  File "/home/ibm_mq/datadog_checks/ibm_mq/collectors/stats_collector.py", line 6, in <module>
    from pymqi.CMQCFC import MQCMD_STATISTICS_CHANNEL, MQCMD_STATISTICS_Q
  File "/opt/datadog-agent/embedded/lib/python3.13/site-packages/pymqi/__init__.py", line 95, in <module>
    import ctypes
  File "/opt/datadog-agent/embedded/lib/python3.13/ctypes/__init__.py", line 10, in <module>
    from _ctypes import Union, Structure, Array
ModuleNotFoundError: No module named '_ctypes'

That definitely seems related to this PR, I'll investigate

chouquette · 2026-01-15T09:52:22Z

/trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable DEPLOY_AGENT=true --variable RUN_UNIT_TESTS=on --variable RUN_KMT_TESTS=on

gh-worker-devflow-routing-ef8351 · 2026-01-15T09:52:25Z

View all feedbacks in Devflow UI.

2026-01-15 09:52:25 UTC ℹ️ Start processing command /trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable DEPLOY_AGENT=true --variable RUN_UNIT_TESTS=on --variable RUN_KMT_TESTS=on

2026-01-15 09:53:42 UTC ℹ️ Gitlab pipeline started

Started pipeline #90839467

chouquette · 2026-01-15T14:57:55Z

/trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable RUN_UNIT_TESTS=on --variable RUN_KMT_TESTS=on

chouquette · 2026-01-15T14:57:55Z

/trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable DEPLOY_AGENT=true --variable RUN_UNIT_TESTS=on --variable RUN_KMT_TESTS=on

gh-worker-devflow-routing-ef8351 · 2026-01-15T14:57:57Z

View all feedbacks in Devflow UI.

2026-01-15 14:57:57 UTC ℹ️ Start processing command /trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable RUN_UNIT_TESTS=on --variable RUN_KMT_TESTS=on

2026-01-15 14:58:15 UTC ℹ️ Branch synced on Gitlab

Branch chouquette/bazel/python3_rfcc was out-of-sync on Gitlab - it has been resynced

2026-01-15 14:59:30 UTC ℹ️ Gitlab pipeline started

Started pipeline #90892541

gh-worker-devflow-routing-ef8351 · 2026-01-15T14:58:04Z

View all feedbacks in Devflow UI.

2026-01-15 14:57:58 UTC ℹ️ Start processing command /trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable DEPLOY_AGENT=true --variable RUN_UNIT_TESTS=on --variable RUN_KMT_TESTS=on
If you need support, contact us on Slack #devflow!

2026-01-15 14:58:01 UTC 🚨 Devflow

child workflow execution already started

Details

child workflow execution error (type: devtools.Devtools_TriggerCiFromPr, workflowID: 5a1bc2e2-11a5-4732-9b9c-c8689183ea6a_32, runID: 56fa589b-0ae4-43b2-84cf-531f3657e7e3, initiatedEventID: 32, startedEventID: 33): child workflow execution error (type: devtools.Devtools_TriggerCi, workflowID: 56fa589b-0ae4-43b2-84cf-531f3657e7e3_14, runID: a935f3ae-51f2-4fc5-bc0c-2e414b4b849b, initiatedEventID: 14, startedEventID: 15): child workflow execution error (type: codesync.CodeSync_ResyncCode, workflowID: devflow-resync:DataDog/datadog-agent:chouquette/bazel/python3_rfcc, runID: , initiatedEventID: 26, startedEventID: 0): child workflow execution already started (type: ChildWorkflowExecutionAlreadyStartedError, retryable: true)

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

chouquette · 2026-01-15T15:09:42Z

/trigger-ci --variable RUN_ALL_BUILDS=true --variable RUN_KITCHEN_TESTS=true --variable RUN_E2E_TESTS=on --variable DEPLOY_AGENT=true --variable RUN_UNIT_TESTS=on --variable RUN_KMT_TESTS=on

This was done in the omnibus recipe, but we don't use the installed file when building with bazel. This resulted in the python module linking to an unsigned shared library, causing the loading process to be instantly killed by macOS on apple silicon

-isystem causes gcc not to be able to find any header

we need to have them all, including those added by our integrations, and filter them after listing them all to .py_compiled_files.txt

chouquette · 2026-01-27T07:29:09Z

For safety, I would probably split it in two PRs. One to make it work, then one to replace in omnibus. But... YOLO.

That would cause the bazel built python not to be used, so we'd have no real guaranty that it actually works no?

chouquette · 2026-01-27T10:33:51Z

/merge

gh-worker-devflow-routing-ef8351 · 2026-01-27T10:33:56Z

View all feedbacks in Devflow UI.

2026-01-27 10:33:55 UTC ℹ️ Start processing command /merge

2026-01-27 10:34:00 UTC ℹ️ MergeQueue: pull request added to the queue

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

2026-01-27 11:18:17 UTC ℹ️ MergeQueue: This merge request was merged

chouquette added the changelog/no-changelog No changelog entry needed label Jan 9, 2026

chouquette requested a review from a team as a code owner January 9, 2026 08:02

chouquette added the qa/no-code-change No code change in Agent code requiring validation label Jan 9, 2026

github-actions bot added medium review PR review might take time team/agent-build labels Jan 9, 2026

chouquette changed the title ~~Chouquette/bazel/python3 rfcc~~ Build python with bazel Jan 9, 2026

chouquette added the ask-review Ask required teams to review this PR label Jan 9, 2026

chouquette changed the title ~~Build python with bazel~~ Build python with bazel on unix as well Jan 9, 2026

chouquette force-pushed the chouquette/bazel/python3_rfcc branch from 0fa7d5a to fa9264f Compare January 9, 2026 10:27

aiuto reviewed Jan 12, 2026

View reviewed changes

chouquette force-pushed the chouquette/bazel/python3_rfcc branch 5 times, most recently from 5d89ffa to ef2c0e9 Compare January 14, 2026 13:24

chouquette and others added 21 commits January 27, 2026 08:10

attempt to fix windows install

23071cd

don't build python_unix on windows

b3924ab

replace_prefix fixup

758dfaa

fix symlink to libpython3.XX.so

f1385ca

fix workaround on macOS

2e94975

fix python dependency providing

772870d

patch sysconfigdata to allow python module to be built down the line

ead8645

also override build flags

fa114c8

-isystem causes gcc not to be able to find any header

don't copy exe & test files

5fa396d

generate py_compiled_files from bazel

6ee786e

don't filter pyc files early

1652c05

we need to have them all, including those added by our integrations, and filter them after listing them all to .py_compiled_files.txt

use the same permissions as before for libs

62cb026

parameterize python version in path

195b7ab

don't copy the python3 executable

7c7da49

fix more permissions

510b4a6

don't enable PGO for python just yet

3fbbc7c

fixup permissions

15a2dc4

use the same optimization level as omnibus

41fb394

simplify file exclusion

f3823d6

don't install Makefile's

c888e16

chouquette force-pushed the chouquette/bazel/python3_rfcc branch from 13ddf83 to c888e16 Compare January 27, 2026 07:13

apply review comments

4677c0a

gh-worker-dd-mergequeue-cf854d bot merged commit e60d3e3 into main Jan 27, 2026
437 checks passed

gh-worker-dd-mergequeue-cf854d bot deleted the chouquette/bazel/python3_rfcc branch January 27, 2026 11:18

github-actions bot locked and limited conversation to collaborators Jan 27, 2026

github-actions bot added this to the 7.77.0 milestone Jan 27, 2026

Conversation

chouquette commented Jan 9, 2026

What does this PR do?

Motivation

Describe how you validated your changes

Additional Notes

Uh oh!

chouquette commented Jan 9, 2026

Uh oh!

dd-devflow-routing-codex bot commented Jan 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

cit-pr-commenter bot commented Jan 9, 2026 • edited by cit-pr-commenter-54b7da bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Regression Detector

Regression Detector Results

❌ Experiments with retried target crashes

Optimization Goals: ✅ No significant changes detected

Experiments ignored for regressions

Fine details of change detection per experiment

Bounds Checks: ✅ Passed

Explanation

Replicate Execution Details

❌ Retried Normal Replicate Execution Failures (non-profiling)

CI Pass/Fail Decision

Uh oh!

agent-platform-auto-pr bot commented Jan 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Static quality checks

Info

Uh oh!

aiuto left a comment

Choose a reason for hiding this comment

Uh oh!

chouquette commented Jan 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

chouquette commented Jan 14, 2026

Uh oh!

gh-worker-devflow-routing-ef8351 bot commented Jan 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

chouquette commented Jan 15, 2026

Uh oh!

chouquette commented Jan 15, 2026

Uh oh!

gh-worker-devflow-routing-ef8351 bot commented Jan 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

chouquette commented Jan 15, 2026

Uh oh!

chouquette commented Jan 15, 2026

Uh oh!

gh-worker-devflow-routing-ef8351 bot commented Jan 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gh-worker-devflow-routing-ef8351 bot commented Jan 15, 2026

Uh oh!

chouquette commented Jan 15, 2026

Uh oh!

chouquette commented Jan 27, 2026

Uh oh!

chouquette commented Jan 27, 2026

Uh oh!

gh-worker-devflow-routing-ef8351 bot commented Jan 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

dd-devflow-routing-codex bot commented Jan 9, 2026 •

edited

Loading

cit-pr-commenter bot commented Jan 9, 2026 •

edited by cit-pr-commenter-54b7da bot

Loading

agent-platform-auto-pr bot commented Jan 9, 2026 •

edited

Loading

chouquette commented Jan 14, 2026 •

edited

Loading

gh-worker-devflow-routing-ef8351 bot commented Jan 14, 2026 •

edited

Loading

gh-worker-devflow-routing-ef8351 bot commented Jan 15, 2026 •

edited

Loading

gh-worker-devflow-routing-ef8351 bot commented Jan 15, 2026 •

edited

Loading

gh-worker-devflow-routing-ef8351 bot commented Jan 27, 2026 •

edited

Loading