Skip to content

[Flexible Outputs] Allow multi-output matching #12010

[Flexible Outputs] Allow multi-output matching

[Flexible Outputs] Allow multi-output matching #12010

Re-run triggered March 30, 2026 17:12
Status Failure
Total duration 6h 10m 59s
Artifacts

main.yaml

on: pull_request
update_readme
7s
update_readme
Matrix: build_docs
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

23 errors and 5 warnings
test (ubuntu-latest, py311-onnx-ir-git)
The operation was canceled.
test (ubuntu-latest, py311)
The operation was canceled.
test (windows-latest, py312)
Out of memory.
test (ubuntu-latest, py311-ort-nightly)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
test (ubuntu-latest, py312)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
test (ubuntu-latest, py311-onnx-weekly)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
test (ubuntu-latest, py310)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
test (ubuntu-latest, py311-torch-nightly)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
test (windows-latest, py310)
Out of memory.
test (windows-latest, py311-onnx-ir-git)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
test (windows-latest, py311-torch-nightly)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
test (windows-latest, py311)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
test (windows-latest, py311-onnx-weekly)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
test (windows-latest, py311-ort-nightly)
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
test (macos-latest, py312)
The job has exceeded the maximum execution time of 6h0m0s
test (macos-latest, py312)
The operation was canceled.
test (macos-latest, py311)
The job has exceeded the maximum execution time of 6h0m0s
test (macos-latest, py311)
The operation was canceled.
test (macos-latest, py311-torch-nightly)
The job has exceeded the maximum execution time of 6h0m0s
test (macos-latest, py310)
The job has exceeded the maximum execution time of 6h0m0s
test (macos-latest, py311-onnx-weekly)
The job has exceeded the maximum execution time of 6h0m0s
test (macos-latest, py311-onnx-ir-git)
The job has exceeded the maximum execution time of 6h0m0s
test (macos-latest, py311-ort-nightly)
The job has exceeded the maximum execution time of 6h0m0s
update_readme
The `python-version` input is not set. The version of Python currently in `PATH` will be used.
test (macos-latest, py312)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (macos-latest, py312)
No files were found with the provided path: error_reports. No artifacts will be uploaded.
test (macos-latest, py311)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test (macos-latest, py311)
No files were found with the provided path: error_reports. No artifacts will be uploaded.