Skip to content

Mark ~CPUCachingAllocator override - #22295

Open
doggeral wants to merge 1 commit into
pytorch:mainfrom
doggeral:export-D117944096
Open

Mark ~CPUCachingAllocator override#22295
doggeral wants to merge 1 commit into
pytorch:mainfrom
doggeral:export-D117944096

Conversation

@doggeral

Copy link
Copy Markdown
Contributor

Summary:
MemoryAllocator declares a virtual destructor, so ~CPUCachingAllocator
already overrides it implicitly. Without the keyword,
-Winconsistent-missing-destructor-override fires, and it is -Werror on the
iphoneos configs, which breaks every Apple build that reaches this header.

Differential Revision: D117944096

Summary:
MemoryAllocator declares a virtual destructor, so ~CPUCachingAllocator
already overrides it implicitly. Without the keyword,
-Winconsistent-missing-destructor-override fires, and it is -Werror on the
iphoneos configs, which breaks every Apple build that reaches this header.

Differential Revision: D117944096
@pytorch-bot

pytorch-bot Bot commented Aug 29, 2026

Copy link
Copy Markdown

🔗 Helpful Links

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

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

❌ 4 New Failures, 1 Unrelated Failure

As of commit 22423cc with merge base 3353bd5 (image):

NEW FAILURES - The following jobs have failed:

  • Cadence Build & Test / hifi-build / hifi4 (gh)
    ##[error]Refusing to check out fork pull request code from a 'pull_request_target' workflow. This workflow runs with the base repository's GITHUB_TOKEN, secrets, default-branch cache scope, and runner access. Fetching and executing a fork's code in that trusted context commonly leads to "pwn request" vulnerabilities. To opt in, review the risks at https://gh.io/securely-using-pull_request_target and set 'allow-unsafe-pr-checkout: true' on the actions/checkout step.
  • Cadence Build & Test / vision-build / vision (gh)
    ##[error]Refusing to check out fork pull request code from a 'pull_request_target' workflow. This workflow runs with the base repository's GITHUB_TOKEN, secrets, default-branch cache scope, and runner access. Fetching and executing a fork's code in that trusted context commonly leads to "pwn request" vulnerabilities. To opt in, review the risks at https://gh.io/securely-using-pull_request_target and set 'allow-unsafe-pr-checkout: true' on the actions/checkout step.
  • pull / android / build-android (gh)
  • pull / test-llama-runner-linux (fp32, xnnpack+quantize_kv, linux.2xlarge, executorch-ubuntu-22.04-clang12) / linux-job (gh)
    ##[error]fatal: unable to access 'https://github.com/zeux/volk/': Error in the HTTP2 framing layer

FLAKY - The following job failed but was likely due to flakiness present on trunk:

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 29, 2026
@meta-codesync

meta-codesync Bot commented Aug 29, 2026

Copy link
Copy Markdown
Contributor

@doggeral has exported this pull request. If you are a Meta employee, you can view the originating Diff in D117944096.

@github-actions

Copy link
Copy Markdown

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.

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. meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant