ONNX CI workflow is broken
See original GitHub issueSince the 5th of May our CI workflow for ONNX is broken (commit 970ba3555794d163daca0ab95240d21e3035c304). Looking at the warnings emitted by the failing tests
WARNING: The shape inference of prim::Constant type is missing, so it may result in wrong shape inference for the exported graph. Please consider adding it in symbolic function.
[...]
AssertionError: The values for attribute 'shape' do not match: torch.Size([1, 4]) != torch.Size([0, 4]).
Two models are affected faster_rcnn
and mask_rcnn
. To reproduce run:
pytest test/test_onnx.py -k "test_faster_rcnn"
pytest test/test_onnx.py -k "test_mask_rcnn"
I believe a recent patch to primtorch might be the offender here. cc @neginraoof @seemethere @mruberry
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:17 (10 by maintainers)
Top Results From Across the Web
Actions · onnx/models
Showing runs from all workflows named Weekly CI with onnx.checker ... [WIP] Update broken test_data_set by the latest ORT Weekly CI with onnx.checker...
Read more >GitHub Action workflow not running
In my case what I needed to run a workflow in pylint branch but it was not working until I added the ...
Read more >GitHub Actions Tutorial and Examples
Learn to create your first GitHub Actions Workflow in our tutorial, and see code examples: building Python project, pushing Docker image, and testing...
Read more >Github Actions Security Best Practices
A workflow file constitutes one or more jobs, and each job is broken down into steps. A step can either execute commands on...
Read more >7 Github Actions Tricks I Wish I Knew Before I Started
These tricks helped me create a more maintainable workflows code. ... Now imagine you need to setup a massive CI/CD workflow.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
After some painful bisection, I finally found the real offender: pytorch/pytorch#73284. After seeing that the PR title contains the phrase ONNX and our ONNX tests are failing, I have no idea how I missed that when looking at the PRs 🤦
Can confirm @BowenBao’s assessment. You can verify yourself, by looking at the
nightly
branch. The cutoff for today (2022-05-13) was pytorch/pytorch@65f71c0cbeb080c13e927d37b0d23d39bac6f092. Taking that knowledge to themaster
branch, we can verify that pytorch/pytorch@a812c4cd96d94d51627d2af290ae87de34169ec0 was three commits late.It will make its way into tomorrows nightly. I’ll retest and close this if the fix worked.