Skip to content

Conversation

@mergennachin
Copy link
Contributor

No description provided.

@pytorch-bot
Copy link

pytorch-bot bot commented Mar 14, 2025

🔗 Helpful Links

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

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

❌ 1 New Failure

As of commit b843749 with merge base b158753 (image):

NEW FAILURE - The following job has failed:

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 Mar 14, 2025
@mergennachin mergennachin requested a review from swolchok March 14, 2025 00:43
@mergennachin
Copy link
Contributor Author

mergennachin commented Mar 14, 2025

@swolchok
Copy link
Contributor

Hmm.. compilation is failing for arm64. Probably a good thing we caught this.

https://github.com/pytorch/executorch/actions/runs/13847352135/job/38748447351?pr=9252

FWIW, the other two are succeeding:

https://github.com/pytorch/executorch/actions/runs/13847352135/job/38748444523?pr=9252

https://github.com/pytorch/executorch/actions/runs/13847352135/job/38748444854?pr=9252

looks like it might be a false positive. see e.g. microsoft/onnxruntime#19296 . I don't see a problem offhand looking at the code, do you?

# threshold=48120 on devserver with gcc11.4
# todo(lfq): update once binary size is below 50kb.
threshold="51784"
threshold="51504"
Copy link
Contributor

Choose a reason for hiding this comment

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

it's awkward that we have the same threshold for two different CPU architectures, but this is still an incremental improvement

@facebook-github-bot
Copy link
Contributor

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

@mergennachin mergennachin marked this pull request as draft March 27, 2025 15:49
@facebook-github-bot
Copy link
Contributor

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


# TODO(#8357): Remove -Wno-int-in-bool-context
COMMON_CXXFLAGS="-fno-exceptions -fno-rtti -Wall -Werror -Wno-int-in-bool-context"
COMMON_CXXFLAGS="-fno-exceptions -fno-rtti -Wall -Werror -Wno-int-in-bool-context -Wno-stringop-overread"
Copy link
Contributor

Choose a reason for hiding this comment

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

Ah this, I thought I removed the memcpy which trigged this for Arm baremetal build.

threshold: 51784
- runner: linux.arm64.2xlarge
docker-image: executorch-ubuntu-22.04-gcc11-aarch64
threshold: 51784
Copy link
Contributor

Choose a reason for hiding this comment

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

We have a big section ~32KiB IIRC for operator registration static arrays, we should not count that towards this. I have a WIP bare metal build where I can see ET text is ~11KiB, that is a good threshold to track IMHO. But this is a step in the right direction. Thanks.

@github-actions
Copy link

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

@github-actions github-actions bot added the stale PRs inactive for over 60 days label Aug 31, 2025
@github-actions
Copy link

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@github-actions
Copy link

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

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. stale PRs inactive for over 60 days topic: not user facing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants