NOCOMMIT: PoC: vectorize just expm1 by swolchok · Pull Request #9586 · pytorch/executorch

swolchok · 2025-03-25T17:05:40Z

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the unary_ufunc_* ops.

[ghstack-poisoned]

swolchok · 2025-03-25T17:05:42Z

Stack from ghstack (oldest at bottom):

pytorch-bot · 2025-03-25T17:05:44Z

🔗 Helpful Links

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

📄 Preview Python docs built from this PR

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

❌ 2 New Failures, 1 Cancelled Job

As of commit 6c7c0e6 with merge base 644b7dd ():

NEW FAILURES - The following jobs have failed:

Build documentation / build (buck2) / Build doc (gh)
RuntimeError: Command docker exec -t a9193e01721040cafa8d30d85869343895ee65bfd71f718e4933f67ce1ac6981 /exec failed with exit code 3
Lint / lintrunner / linux-job (gh)
RuntimeError: Command docker exec -t 4cbb64943f6f3a74e79a0aa7491fda92ee777be51d28d4a48dd8a7bf41de550b /exec failed with exit code 2

CANCELLED JOB - The following job was cancelled. Please retry:

pull (gh)

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

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: 94797d6 ghstack-comment-id: 2751961712 Pull Request resolved: #9586

[ghstack-poisoned]

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: e65c2b0 ghstack-comment-id: 2751961712 Pull Request resolved: #9586

I ran into an issue reordering diffs in a direct stack (the one currently ending in pytorch/executorch#9586) where GitHub's API complained `There are no new commits between base branch 'gh/swolchok/395/head' and head branch 'gh/swolchok/383/head'`. This seems to have fixed it for me.

swolchok · 2025-04-02T02:14:11Z

 namespace executor {
 namespace native {

+// REVIEW: I'm not entirely sure what the best way to implement this


either the original vectorization PR or a preliminary PR will address this

swolchok · 2025-05-28T23:45:02Z

this is getting folded into #9386

swolchok · 2025-03-25T17:05:40Z

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the unary_ufunc_* ops.

[ghstack-poisoned]

swolchok · 2025-03-25T17:05:42Z

Stack from ghstack (oldest at bottom):

pytorch-bot · 2025-03-25T17:05:44Z

🔗 Helpful Links

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

📄 Preview Python docs built from this PR

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

❌ 2 New Failures, 1 Cancelled Job

As of commit 6c7c0e6 with merge base 644b7dd ():

NEW FAILURES - The following jobs have failed:

Build documentation / build (buck2) / Build doc (gh)
RuntimeError: Command docker exec -t a9193e01721040cafa8d30d85869343895ee65bfd71f718e4933f67ce1ac6981 /exec failed with exit code 3
Lint / lintrunner / linux-job (gh)
RuntimeError: Command docker exec -t 4cbb64943f6f3a74e79a0aa7491fda92ee777be51d28d4a48dd8a7bf41de550b /exec failed with exit code 2

CANCELLED JOB - The following job was cancelled. Please retry:

pull (gh)

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

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: 94797d6 ghstack-comment-id: 2751961712 Pull Request resolved: #9586

[ghstack-poisoned]

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: e65c2b0 ghstack-comment-id: 2751961712 Pull Request resolved: #9586

I ran into an issue reordering diffs in a direct stack (the one currently ending in pytorch/executorch#9586) where GitHub's API complained `There are no new commits between base branch 'gh/swolchok/395/head' and head branch 'gh/swolchok/383/head'`. This seems to have fixed it for me.

swolchok · 2025-04-02T02:14:11Z

 namespace executor {
 namespace native {

+// REVIEW: I'm not entirely sure what the best way to implement this


either the original vectorization PR or a preliminary PR will address this

swolchok · 2025-05-28T23:45:02Z

this is getting folded into #9386

swolchok · 2025-03-25T17:05:40Z

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the unary_ufunc_* ops.

[ghstack-poisoned]

swolchok · 2025-03-25T17:05:42Z

Stack from ghstack (oldest at bottom):

pytorch-bot · 2025-03-25T17:05:44Z

🔗 Helpful Links

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

📄 Preview Python docs built from this PR

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

❌ 2 New Failures, 1 Cancelled Job

As of commit 6c7c0e6 with merge base 644b7dd ():

NEW FAILURES - The following jobs have failed:

Build documentation / build (buck2) / Build doc (gh)
RuntimeError: Command docker exec -t a9193e01721040cafa8d30d85869343895ee65bfd71f718e4933f67ce1ac6981 /exec failed with exit code 3
Lint / lintrunner / linux-job (gh)
RuntimeError: Command docker exec -t 4cbb64943f6f3a74e79a0aa7491fda92ee777be51d28d4a48dd8a7bf41de550b /exec failed with exit code 2

CANCELLED JOB - The following job was cancelled. Please retry:

pull (gh)

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

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: 94797d6 ghstack-comment-id: 2751961712 Pull Request resolved: #9586

[ghstack-poisoned]

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: e65c2b0 ghstack-comment-id: 2751961712 Pull Request resolved: #9586

I ran into an issue reordering diffs in a direct stack (the one currently ending in pytorch/executorch#9586) where GitHub's API complained `There are no new commits between base branch 'gh/swolchok/395/head' and head branch 'gh/swolchok/383/head'`. This seems to have fixed it for me.

swolchok · 2025-04-02T02:14:11Z

 namespace executor {
 namespace native {

+// REVIEW: I'm not entirely sure what the best way to implement this


either the original vectorization PR or a preliminary PR will address this

swolchok · 2025-05-28T23:45:02Z

this is getting folded into #9386

swolchok · 2025-03-25T17:05:40Z

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the unary_ufunc_* ops.

[ghstack-poisoned]

swolchok · 2025-03-25T17:05:42Z

Stack from ghstack (oldest at bottom):

pytorch-bot · 2025-03-25T17:05:44Z

🔗 Helpful Links

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

📄 Preview Python docs built from this PR

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

❌ 2 New Failures, 1 Cancelled Job

As of commit 6c7c0e6 with merge base 644b7dd ():

NEW FAILURES - The following jobs have failed:

Build documentation / build (buck2) / Build doc (gh)
RuntimeError: Command docker exec -t a9193e01721040cafa8d30d85869343895ee65bfd71f718e4933f67ce1ac6981 /exec failed with exit code 3
Lint / lintrunner / linux-job (gh)
RuntimeError: Command docker exec -t 4cbb64943f6f3a74e79a0aa7491fda92ee777be51d28d4a48dd8a7bf41de550b /exec failed with exit code 2

CANCELLED JOB - The following job was cancelled. Please retry:

pull (gh)

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

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: 94797d6 ghstack-comment-id: 2751961712 Pull Request resolved: #9586

[ghstack-poisoned]

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: e65c2b0 ghstack-comment-id: 2751961712 Pull Request resolved: #9586

I ran into an issue reordering diffs in a direct stack (the one currently ending in pytorch/executorch#9586) where GitHub's API complained `There are no new commits between base branch 'gh/swolchok/395/head' and head branch 'gh/swolchok/383/head'`. This seems to have fixed it for me.

swolchok · 2025-04-02T02:14:11Z

 namespace executor {
 namespace native {

+// REVIEW: I'm not entirely sure what the best way to implement this


either the original vectorization PR or a preliminary PR will address this

swolchok · 2025-05-28T23:45:02Z

this is getting folded into #9386

swolchok · 2025-03-25T17:05:40Z

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the unary_ufunc_* ops.

[ghstack-poisoned]

swolchok · 2025-03-25T17:05:42Z

Stack from ghstack (oldest at bottom):

pytorch-bot · 2025-03-25T17:05:44Z

🔗 Helpful Links

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

📄 Preview Python docs built from this PR

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

❌ 2 New Failures, 1 Cancelled Job

As of commit 6c7c0e6 with merge base 644b7dd ():

NEW FAILURES - The following jobs have failed:

Build documentation / build (buck2) / Build doc (gh)
RuntimeError: Command docker exec -t a9193e01721040cafa8d30d85869343895ee65bfd71f718e4933f67ce1ac6981 /exec failed with exit code 3
Lint / lintrunner / linux-job (gh)
RuntimeError: Command docker exec -t 4cbb64943f6f3a74e79a0aa7491fda92ee777be51d28d4a48dd8a7bf41de550b /exec failed with exit code 2

CANCELLED JOB - The following job was cancelled. Please retry:

pull (gh)

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

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: 94797d6 ghstack-comment-id: 2751961712 Pull Request resolved: #9586

[ghstack-poisoned]

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: e65c2b0 ghstack-comment-id: 2751961712 Pull Request resolved: #9586

I ran into an issue reordering diffs in a direct stack (the one currently ending in pytorch/executorch#9586) where GitHub's API complained `There are no new commits between base branch 'gh/swolchok/395/head' and head branch 'gh/swolchok/383/head'`. This seems to have fixed it for me.

swolchok · 2025-04-02T02:14:11Z

 namespace executor {
 namespace native {

+// REVIEW: I'm not entirely sure what the best way to implement this


either the original vectorization PR or a preliminary PR will address this

swolchok · 2025-05-28T23:45:02Z

this is getting folded into #9386

swolchok · 2025-03-25T17:05:40Z

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the unary_ufunc_* ops.

[ghstack-poisoned]

swolchok · 2025-03-25T17:05:42Z

Stack from ghstack (oldest at bottom):

pytorch-bot · 2025-03-25T17:05:44Z

🔗 Helpful Links

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

📄 Preview Python docs built from this PR

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

❌ 2 New Failures, 1 Cancelled Job

As of commit 6c7c0e6 with merge base 644b7dd ():

NEW FAILURES - The following jobs have failed:

Build documentation / build (buck2) / Build doc (gh)
RuntimeError: Command docker exec -t a9193e01721040cafa8d30d85869343895ee65bfd71f718e4933f67ce1ac6981 /exec failed with exit code 3
Lint / lintrunner / linux-job (gh)
RuntimeError: Command docker exec -t 4cbb64943f6f3a74e79a0aa7491fda92ee777be51d28d4a48dd8a7bf41de550b /exec failed with exit code 2

CANCELLED JOB - The following job was cancelled. Please retry:

pull (gh)

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

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: 94797d6 ghstack-comment-id: 2751961712 Pull Request resolved: #9586

[ghstack-poisoned]

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: e65c2b0 ghstack-comment-id: 2751961712 Pull Request resolved: #9586

I ran into an issue reordering diffs in a direct stack (the one currently ending in pytorch/executorch#9586) where GitHub's API complained `There are no new commits between base branch 'gh/swolchok/395/head' and head branch 'gh/swolchok/383/head'`. This seems to have fixed it for me.

swolchok · 2025-04-02T02:14:11Z

 namespace executor {
 namespace native {

+// REVIEW: I'm not entirely sure what the best way to implement this


either the original vectorization PR or a preliminary PR will address this

swolchok · 2025-05-28T23:45:02Z

this is getting folded into #9386

swolchok · 2025-03-25T17:05:40Z

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the unary_ufunc_* ops.

[ghstack-poisoned]

swolchok · 2025-03-25T17:05:42Z

Stack from ghstack (oldest at bottom):

pytorch-bot · 2025-03-25T17:05:44Z

🔗 Helpful Links

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

📄 Preview Python docs built from this PR

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

❌ 2 New Failures, 1 Cancelled Job

As of commit 6c7c0e6 with merge base 644b7dd ():

NEW FAILURES - The following jobs have failed:

Build documentation / build (buck2) / Build doc (gh)
RuntimeError: Command docker exec -t a9193e01721040cafa8d30d85869343895ee65bfd71f718e4933f67ce1ac6981 /exec failed with exit code 3
Lint / lintrunner / linux-job (gh)
RuntimeError: Command docker exec -t 4cbb64943f6f3a74e79a0aa7491fda92ee777be51d28d4a48dd8a7bf41de550b /exec failed with exit code 2

CANCELLED JOB - The following job was cancelled. Please retry:

pull (gh)

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

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: 94797d6 ghstack-comment-id: 2751961712 Pull Request resolved: #9586

[ghstack-poisoned]

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: e65c2b0 ghstack-comment-id: 2751961712 Pull Request resolved: #9586

I ran into an issue reordering diffs in a direct stack (the one currently ending in pytorch/executorch#9586) where GitHub's API complained `There are no new commits between base branch 'gh/swolchok/395/head' and head branch 'gh/swolchok/383/head'`. This seems to have fixed it for me.

swolchok · 2025-04-02T02:14:11Z

 namespace executor {
 namespace native {

+// REVIEW: I'm not entirely sure what the best way to implement this


either the original vectorization PR or a preliminary PR will address this

swolchok · 2025-05-28T23:45:02Z

this is getting folded into #9386

swolchok · 2025-03-25T17:05:40Z

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the unary_ufunc_* ops.

[ghstack-poisoned]

swolchok · 2025-03-25T17:05:42Z

Stack from ghstack (oldest at bottom):

pytorch-bot · 2025-03-25T17:05:44Z

🔗 Helpful Links

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

📄 Preview Python docs built from this PR

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

❌ 2 New Failures, 1 Cancelled Job

As of commit 6c7c0e6 with merge base 644b7dd ():

NEW FAILURES - The following jobs have failed:

Build documentation / build (buck2) / Build doc (gh)
RuntimeError: Command docker exec -t a9193e01721040cafa8d30d85869343895ee65bfd71f718e4933f67ce1ac6981 /exec failed with exit code 3
Lint / lintrunner / linux-job (gh)
RuntimeError: Command docker exec -t 4cbb64943f6f3a74e79a0aa7491fda92ee777be51d28d4a48dd8a7bf41de550b /exec failed with exit code 2

CANCELLED JOB - The following job was cancelled. Please retry:

pull (gh)

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

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: 94797d6 ghstack-comment-id: 2751961712 Pull Request resolved: #9586

[ghstack-poisoned]

Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: e65c2b0 ghstack-comment-id: 2751961712 Pull Request resolved: #9586

I ran into an issue reordering diffs in a direct stack (the one currently ending in pytorch/executorch#9586) where GitHub's API complained `There are no new commits between base branch 'gh/swolchok/395/head' and head branch 'gh/swolchok/383/head'`. This seems to have fixed it for me.

swolchok · 2025-04-02T02:14:11Z

 namespace executor {
 namespace native {

+// REVIEW: I'm not entirely sure what the best way to implement this


either the original vectorization PR or a preliminary PR will address this

swolchok · 2025-05-28T23:45:02Z

this is getting folded into #9386

Update
bfd122c
[ghstack-poisoned]

swolchok requested a review from manuelcandales as a code owner March 25, 2025 17:05

swolchok marked this pull request as draft March 25, 2025 17:06

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 Mar 25, 2025

Update
6c7c0e6
[ghstack-poisoned]

swolchok mentioned this pull request Mar 25, 2025
RFC: Push diffs in Git before telling GitHub about it ezyang/ghstack#280
Merged

swolchok commented Apr 2, 2025
View reviewed changes

swolchok closed this May 28, 2025

Update
bfd122c
[ghstack-poisoned]

swolchok requested a review from manuelcandales as a code owner March 25, 2025 17:05

swolchok marked this pull request as draft March 25, 2025 17:06

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 Mar 25, 2025

Update
6c7c0e6
[ghstack-poisoned]

swolchok mentioned this pull request Mar 25, 2025
RFC: Push diffs in Git before telling GitHub about it ezyang/ghstack#280
Merged

swolchok commented Apr 2, 2025
View reviewed changes

swolchok closed this May 28, 2025

Update
bfd122c
[ghstack-poisoned]

swolchok requested a review from manuelcandales as a code owner March 25, 2025 17:05

swolchok marked this pull request as draft March 25, 2025 17:06

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 Mar 25, 2025

Update
6c7c0e6
[ghstack-poisoned]

swolchok mentioned this pull request Mar 25, 2025
RFC: Push diffs in Git before telling GitHub about it ezyang/ghstack#280
Merged

swolchok commented Apr 2, 2025
View reviewed changes

swolchok closed this May 28, 2025

Update
bfd122c
[ghstack-poisoned]

swolchok requested a review from manuelcandales as a code owner March 25, 2025 17:05

swolchok marked this pull request as draft March 25, 2025 17:06

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 Mar 25, 2025

Update
6c7c0e6
[ghstack-poisoned]

swolchok mentioned this pull request Mar 25, 2025
RFC: Push diffs in Git before telling GitHub about it ezyang/ghstack#280
Merged

swolchok commented Apr 2, 2025
View reviewed changes

swolchok closed this May 28, 2025

Update
bfd122c
[ghstack-poisoned]

swolchok requested a review from manuelcandales as a code owner March 25, 2025 17:05

swolchok marked this pull request as draft March 25, 2025 17:06

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 Mar 25, 2025

Update
6c7c0e6
[ghstack-poisoned]

swolchok mentioned this pull request Mar 25, 2025
RFC: Push diffs in Git before telling GitHub about it ezyang/ghstack#280
Merged

swolchok commented Apr 2, 2025
View reviewed changes

swolchok closed this May 28, 2025

Update
bfd122c
[ghstack-poisoned]

swolchok requested a review from manuelcandales as a code owner March 25, 2025 17:05

swolchok marked this pull request as draft March 25, 2025 17:06

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 Mar 25, 2025

Update
6c7c0e6
[ghstack-poisoned]

swolchok mentioned this pull request Mar 25, 2025
RFC: Push diffs in Git before telling GitHub about it ezyang/ghstack#280
Merged

swolchok commented Apr 2, 2025
View reviewed changes

swolchok closed this May 28, 2025

Update
bfd122c
[ghstack-poisoned]

swolchok requested a review from manuelcandales as a code owner March 25, 2025 17:05

swolchok marked this pull request as draft March 25, 2025 17:06

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 Mar 25, 2025

Update
6c7c0e6
[ghstack-poisoned]

swolchok mentioned this pull request Mar 25, 2025
RFC: Push diffs in Git before telling GitHub about it ezyang/ghstack#280
Merged

swolchok commented Apr 2, 2025
View reviewed changes

swolchok closed this May 28, 2025

Update
bfd122c
[ghstack-poisoned]

swolchok requested a review from manuelcandales as a code owner March 25, 2025 17:05

swolchok marked this pull request as draft March 25, 2025 17:06

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 Mar 25, 2025

Update
6c7c0e6
[ghstack-poisoned]

swolchok mentioned this pull request Mar 25, 2025
RFC: Push diffs in Git before telling GitHub about it ezyang/ghstack#280
Merged

swolchok commented Apr 2, 2025
View reviewed changes

swolchok closed this May 28, 2025

Uh oh!

Conversation

swolchok commented Mar 25, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

swolchok commented Mar 25, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pytorch-botBot commented Mar 25, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔗 Helpful Links

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

❌ 2 New Failures, 1 Cancelled Job

Uh oh!

swolchokApr 2, 2025

Choose a reason for hiding this comment

Uh oh!

swolchok commented May 28, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

swolchok commented Mar 25, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

swolchok commented Mar 25, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pytorch-botBot commented Mar 25, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔗 Helpful Links

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

❌ 2 New Failures, 1 Cancelled Job

Uh oh!

swolchokApr 2, 2025

Choose a reason for hiding this comment

Uh oh!

swolchok commented May 28, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

swolchok commented Mar 25, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

swolchok commented Mar 25, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pytorch-botBot commented Mar 25, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔗 Helpful Links

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

❌ 2 New Failures, 1 Cancelled Job

Uh oh!

swolchokApr 2, 2025

Choose a reason for hiding this comment

Uh oh!

swolchok commented May 28, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

swolchok commented Mar 25, 2025•
edited
Loading

swolchok commented Mar 25, 2025•
edited
Loading

pytorch-botBot commented Mar 25, 2025•
edited
Loading

swolchok commented Mar 25, 2025•
edited
Loading

swolchok commented Mar 25, 2025•
edited
Loading

pytorch-botBot commented Mar 25, 2025•
edited
Loading

swolchok commented Mar 25, 2025•
edited
Loading

swolchok commented Mar 25, 2025•
edited
Loading

pytorch-botBot commented Mar 25, 2025•
edited
Loading

swolchok commented Mar 25, 2025•
edited
Loading

swolchok commented Mar 25, 2025•
edited
Loading

pytorch-botBot commented Mar 25, 2025•
edited
Loading

swolchok commented Mar 25, 2025•
edited
Loading

swolchok commented Mar 25, 2025•
edited
Loading

pytorch-botBot commented Mar 25, 2025•
edited
Loading