Skip to content

Route Harmony reasoning separately from final output#21378

Open
Gasoonjia wants to merge 1 commit into
mainfrom
export-D112991739
Open

Route Harmony reasoning separately from final output#21378
Gasoonjia wants to merge 1 commit into
mainfrom
export-D112991739

Conversation

@Gasoonjia

Copy link
Copy Markdown
Contributor

Summary: Teach the shared OpenAI chat adapter to expose optional reasoning_content.

Differential Revision: D112991739

Summary: Teach the shared OpenAI chat adapter to expose optional reasoning_content.

Differential Revision: D112991739
@pytorch-bot

pytorch-bot Bot commented Jul 24, 2026

Copy link
Copy Markdown

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/21378

Note: Links to docs will display an error until the docs builds have been completed.

❌ 2 New Failures, 3 Pending, 41 Unrelated Failures

As of commit de7290c with merge base e2c9a48 (image):

NEW FAILURES - The following jobs have failed:

  • Build Presets / windows (pybind) / build (gh)
    Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under 'C:\actions-runner\_work\executorch\executorch\test-infra\.github\actions\teardown-windows'. Did you forget to run actions/checkout before running your local action?
  • Test QNN Windows MSVC build / build-qnn-windows-msvc / windows-job (gh)
    Can't find 'action.yml', 'action.yaml' or 'Dockerfile' under 'C:\actions-runner\_work\executorch\executorch\test-infra\.github\actions\teardown-windows'. Did you forget to run actions/checkout before running your local action?

FLAKY - The following jobs failed but were likely due to flakiness present on trunk:

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jul 24, 2026
@meta-codesync

meta-codesync Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

@Gasoonjia has exported this pull request. If you are a Meta employee, you can view the originating Diff in D112991739.

@github-actions

Copy link
Copy Markdown

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant