Skip to content
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

[Arm] Fix tosa-reference model upstream tracking #6156

Closed
wants to merge 1 commit into from

Conversation

digantdesai
Copy link
Contributor

It appears that upstream updates to branch tosa_reference_model/v0.8 which we used to track broke ET CI. Hard coding it to a known good version for now.

Copy link

pytorch-bot bot commented Oct 11, 2024

🔗 Helpful Links

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

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

✅ No Failures

As of commit ca6fc23 with merge base 56a3d1e (image):
💚 Looks good so far! There are no failures yet. 💚

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

@facebook-github-bot facebook-github-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 Oct 11, 2024
@digantdesai digantdesai added partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm ciflow/trunk labels Oct 11, 2024
examples/arm/setup.sh Outdated Show resolved Hide resolved
cd reference_model
git reset --hard ${tosa_reference_model_rev}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

git reset will change what the default branch points to; maybe just

Suggested change
git reset --hard ${tosa_reference_model_rev}
git checkout ${tosa_reference_model_rev}

But the reset will work.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just the detached head warning I don't like with check out, but no strong preference, will update.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reset is fine if you'd rather do that. Stack overflow seems to do either of them. And since we're not making changes to the repo it's not a big deal -- origin/main won't change even with a reset

It appears that upstream updates to branch tosa_reference_model/v0.8 which we used to track broke
ET CI. Hard coding it to a known good version for now.

* Failed CI job - https://github.com/pytorch/executorch/actions/runs/11283289096/job/31382443033#step:12:26700

* Upstream branch updates - https://review.mlplatform.org/q/project:tosa%252Freference_model+branch:v0.80
Potentially culprit gerrit ids - 12676, 12677, 12678 updated today
@digantdesai
Copy link
Contributor Author

digantdesai commented Oct 11, 2024

I will let the CI run for an hour or so then push an update and also a cherry-pick request assuming everything works.

@digantdesai
Copy link
Contributor Author

Arm jobs passed!!

@digantdesai
Copy link
Contributor Author

@pytorchbot cherry-pick --onto release/0.4 -c critical

@facebook-github-bot
Copy link
Contributor

@digantdesai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

@facebook-github-bot
Copy link
Contributor

@digantdesai merged this pull request in 5696b35.

@dvorjackz
Copy link
Contributor

Think you need to do this after it's actually merged into main

@dvorjackz
Copy link
Contributor

@pytorchbot cherry-pick --onto release/0.4 -c critical

pytorchbot pushed a commit that referenced this pull request Oct 11, 2024
Summary:
It appears that upstream updates to branch tosa_reference_model/v0.8 which we used to track broke ET CI. Hard coding it to a known good version for now.

* Failed CI job - https://github.com/pytorch/executorch/actions/runs/11283289096/job/31382443033#step:12:26700

* Upstream branch updates - https://review.mlplatform.org/q/project:tosa%252Freference_model+branch:v0.80 Potentially culprit gerrit ids - 12676, 12677, 12678 updated today

Pull Request resolved: #6156

Reviewed By: larryliu0820

Differential Revision: D64222142

Pulled By: digantdesai

fbshipit-source-id: 8438770851f8309020755992036f8e4c50857301
(cherry picked from commit 5696b35)
@pytorchbot
Copy link
Collaborator

Cherry picking #6156

The cherry pick PR is at #6162 and it is recommended to link a critical cherry pick PR with an issue. The following tracker issues are updated:

Details for Dev Infra team Raised by workflow job

@per
Copy link
Collaborator

per commented Oct 11, 2024

Thanks for sorting that out @digantdesai. Will add the needed fix in handling dequanting the output from the reference model which will fix it for main. Moving the model in controlled steps seems a good addition anyways.

dvorjackz pushed a commit that referenced this pull request Oct 11, 2024
Fix tosa-reference model upstream tracking (#6156)

Summary:
It appears that upstream updates to branch tosa_reference_model/v0.8 which we used to track broke ET CI. Hard coding it to a known good version for now.

* Failed CI job - https://github.com/pytorch/executorch/actions/runs/11283289096/job/31382443033#step:12:26700

* Upstream branch updates - https://review.mlplatform.org/q/project:tosa%252Freference_model+branch:v0.80 Potentially culprit gerrit ids - 12676, 12677, 12678 updated today

Pull Request resolved: #6156

Reviewed By: larryliu0820

Differential Revision: D64222142

Pulled By: digantdesai

fbshipit-source-id: 8438770851f8309020755992036f8e4c50857301
(cherry picked from commit 5696b35)

Co-authored-by: Digant Desai <digantdesai@meta.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Merged partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants