kaxil opened a new pull request, #73149: URL: https://github.com/apache/airflow/pull/73149
Follow-up to #72164, which scoped `[core] execute_tasks_new_python_interpreter` to the task process. The tests around that scope patch the platform gate, `_should_use_exec()`, and assert the value flows through to `WatchedSubprocess.start`; none of them set the option itself. A config read moved back into the shared gate, which is the shape the first revision of #72164 had, would pass the suite while switching the Dag processor and the triggerer to a fresh interpreter per fork. These tests set the option to `True` and to `False` and assert that `DagFileProcessorProcess.start`, `TriggerRunnerSupervisor.start` and `CallbackSubprocess.start` still hand `use_exec=False` to the base `start()`. The Dag processor and triggerer tests run under the existing autouse fixtures that pin the platform gate to bare fork, so they hold on macOS as well as Linux. The callback test needs no pin: its closure target can only run under a bare fork, which is what the assertion protects. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
