9961218e12
CI / benchmark-publish (pull_request) Has been cancelled
CI / benchmark-regression (pull_request) Has been cancelled
CI / lint (pull_request) Successful in 54s
CI / typecheck (pull_request) Successful in 1m19s
CI / security (pull_request) Successful in 1m15s
CI / quality (pull_request) Successful in 51s
CI / push-validation (pull_request) Successful in 38s
CI / helm (pull_request) Successful in 39s
CI / build (pull_request) Successful in 47s
CI / integration_tests (pull_request) Failing after 4m14s
CI / e2e_tests (pull_request) Successful in 4m15s
CI / unit_tests (pull_request) Failing after 5m56s
CI / docker (pull_request) Has been skipped
CI / coverage (pull_request) Has been skipped
CI / status-check (pull_request) Failing after 4s
step_mock_popen_success stored mock_proc (Popen's return value) as context.popen_mock, but call_args is recorded on the mock *replacing* subprocess.Popen (what patcher.start() returns). Reading call_args from mock_proc returns None, causing TypeError in the three command-construction scenarios — behave reports these as "errored" not "failed". Fix: assign patcher.start() to context.popen_mock so the assertion steps read call_args from the correct mock. Also remove the redundant patcher.stop() calls from the assertion Then steps (context.add_cleanup already handles teardown). Add the required @tdd_issue and @tdd_issue_691 tags to the Connect with .py file path scenario per the TDD bug fix workflow. ISSUES CLOSED: #691