-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[ONNX] bump onnx submodule to rel-1.15.0 #110663
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/110663
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 9f435d8 with merge base fb68aa0 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bazel failures are legit
|
I suspect it might be related to this PR: onnx/onnx#5559 |
50233ca to
87d9be8
Compare
|
Looks like that was a new header and a glob for it was missing in the bazel build. |
|
@pytorchbot merge -r |
|
@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here |
|
Successfully rebased |
87d9be8 to
600296c
Compare
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Merge failedReason: 1 mandatory check(s) failed. The first few are: Dig deeper by viewing the failures on hud |
- onnx==1.15.0rc1 - onnxscript==0.1.0.dev20231006 - ort-nightly==1.17.0.dev20231005001
600296c to
9f435d8
Compare
|
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Uh oh!
There was an error while loading. Please reload this page.