LiteLLM sends parallel_tool_calls without tools to Azure OpenAI
- Repository
- openai/openai-agents-python
- Owner
- Assigned owner
- Attempts
- 1 / 1
- Execution cost
- $0.91 / $14
- Understand completedScope and criteria
- Build completedAttempt and checks
- Review completedCode review
- Release completedDeployment record
- Verify outcome current stageCustomer decision
The assigned customer verifies and accepts the result.
Responsible: Customer acceptorStage: Verify outcomeExecution: idleWaiting on customer acceptance
Criteria met on release candidate on 443e1f5113f4 (not merged, not released)
isolated-sandbox · 72c9990e6a98
Code review
Approved- Reviewed commit
72c9990e6a98acb714354cf0bcda0ba6975e4d5e- CI
- Not run · no pull request was opened · the review recorded “passed” without a GitHub CI report
Operator review by Launchway AI (rehearsal; not a review by the repository's maintainers). Read the full diff: the source change moves the parallel_tool_calls decision after function tools and handoffs are converted, sends None when nothing is converted and keeps an explicit True or False otherwise, in 4 added and 7 removed lines of litellm_model.py; the agent also added 18 regression tests in a new test file. No GitHub CI ran because no pull request was opened. The CI field here records Launchway AI's sealed acceptance run: the tests from the project's merged fix (PR #4330) passed on this candidate: 2 of 2 fail-to-pass and 13 of 13 pass-to-pass. Full repository suite on the candidate: 7,814 passed and 2 failed. One of the two also fails at the parent commit (the sandbox mount tool is absent from the container). The other is a timing test that fails 3 of 3 when run alone, on both the parent and the candidate, and passed inside the parent's full-suite run, so it depends on order or timing.
No verified pull request link recorded.
Release
- Version
- candidate on 443e1f5113f4 (not merged, not released)
- Environment
- isolated-sandbox
- Deployment
- openai-agents-python@443e1f5
- Released commit
72c9990e6a98acb714354cf0bcda0ba6975e4d5e- Source
- vendor attested
- Evidence
- Nothing was deployed or pushed. The candidate diff was applied to the parent commit in a fresh --network=none container from the task image; no upstream pull request was opened.
Customer outcome
| Criterion | Result | Observed | Evidence |
|---|---|---|---|
| AC1 · The repository's existing model tests still pass (tests/models). | Passed | Repository model tests passed on the candidate inside the attempt. | Attempt check repository-model-tests: repository-model-tests passed |
| AC2 · The behaviour the issue asks for is implemented. | Passed | Sealed acceptance ACCEPTED: 2/2 fail-to-pass and 13/13 pass-to-pass tests from merged PR #4330 passed. | The PR's own tests, never shown to the agent, run after the attempt in a fresh container. Same tests on the unchanged parent commit: REJECTED (0/2 fail-to-pass). Receipt sealed-acceptance.json, candidate sha256 e0decc6375218273. |
Other workflow actions
Activity
Change created
Human · launchway-operator
Record note
Human · launchway-operator
Investigation started
Human · launchway-operator
Record investigation
Machine · changes-worker
Scope updated
Human · launchway-operator
Scope approved
Human · launchway-operator
Attempt started
Human · launchway-operator
Record candidate
Machine · changes-worker
Record validation
Machine · changes-worker
Review recorded
Human · launchway-operator
Release recorded
Human · launchway-operator
Outcome recorded
Human · launchway-operator
Review recorded
Human · launchway-operator
Release recorded
Human · launchway-operator
Outcome recorded
Human · launchway-operator