executorch
executorch copied to clipboard
Arm backend: [serializer-lib][0.80] Refactor to accomodate v1.0
Stack from ghstack (oldest at bottom):
- (to be filled)
move the directory to tosa_tools/v0.80
Differential Revision: D73642286
:link: Helpful Links
:test_tube: See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/10467
- :page_facing_up: Preview Python docs built from this PR
Note: Links to docs will display an error until the docs builds have been completed.
:x: 4 New Failures
As of commit de2f49b438079ce0fd8398bda2a17e5d84f14ed7 with merge base 143224370c106e8fa5421d4b49d5b28a1a725aff ():
NEW FAILURES - The following jobs have failed:
- Build documentation / check-urls (gh)
Process completed with exit code 1. - Check Labels / Check labels (gh)
RuntimeError: Error checking labels: PR does not have required labels - Propose to merge ghstack orig PRs to main / Try to create a PR with ghstack /orig branch (gh)
Process completed with exit code 1. - trunk / test-models-macos (emformer_join, xnnpack-quantization-delegation) / macos-job (gh)
RuntimeError: Command bash /Users/ec2-user/runner/_work/_temp/exec_script failed with exit code 1
This comment was automatically generated by Dr. CI and updates every 15 minutes.
This PR needs a release notes: label
If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.
If not, please add the topic: not user facing label.
To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"
For more information, see https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.
@digantdesai is this still needed?
@digantdesai is this still needed?
no this was just for testing. closing..