Skip to content

[ET-VK][ez] Move execute node threshold calculation from prepare_pipelines() to prepare() #13478

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

Merged
merged 1 commit into from
Aug 19, 2025

Conversation

SS-JIA
Copy link
Contributor

@SS-JIA SS-JIA commented Aug 18, 2025

Stack from ghstack (oldest at bottom):

Title says it all; prepare() is a more appropriate place for this action than prepare_pipelines().

Motivation

Fix potential floating point exception (divide-by-zero) during tests.

Some tests don't call prepare_pipelines(), which means execute_threshold_node_count_ is unititialized, causing a divide by zero in execute when trying to modulo with execute_threshold_node_count_

Differential Revision: D80468138

…elines()` to `prepare()`

Title says it all; `prepare()` is a more appropriate place for this action than `prepare_pipelines()`.

## Motivation

Fix potential floating point exception (divide-by-zero) during tests.

Some tests don't call `prepare_pipelines()`, which means `execute_threshold_node_count_` is unititialized, causing a divide by zero in execute when trying to modulo with `execute_threshold_node_count_`

Differential Revision: [D80468138](https://our.internmc.facebook.com/intern/diff/D80468138/)

[ghstack-poisoned]
Copy link

pytorch-bot bot commented Aug 18, 2025

🔗 Helpful Links

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

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

❌ 1 New Failure, 1 Unrelated Failure

As of commit 5dc9b50 with merge base 5ff0208 (image):

NEW FAILURE - The following job has failed:

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

  • pull / test-binary-size-linux-gcc / linux-job (gh) (trunk failure)
    /pytorch/executorch/kernels/portable/cpu/op_stack.cpp:129:26: error: comparison of integer expressions of different signedness: ‘size_t’ {aka ‘long unsigned int’} and ‘ssize_t’ {aka ‘long int’} [-Werror=sign-compare]

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

@meta-cla meta-cla 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 Aug 18, 2025
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D80468138

@trivedivivek trivedivivek added the release notes: vulkan Changes to the Vulkan backend delegate label Aug 18, 2025
@facebook-github-bot facebook-github-bot merged commit 2c51198 into gh/SS-JIA/293/base Aug 19, 2025
104 of 109 checks passed
@facebook-github-bot facebook-github-bot deleted the gh/SS-JIA/293/head branch August 19, 2025 02:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported release notes: vulkan Changes to the Vulkan backend delegate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants